Commit a39f5f1

1. Must follow the Docker Remote API interop and breaking change policy (https://docs.docker.com/engine/breaking_changes/)

2. Must work locally or remotely, with remote following appropriate authentication and security mechanisms (i.e. TLS).

* Follow the PowerShell design guidelines (https://msdn.microsoft.com/en-us/library/ms714657(v=vs.85).aspx).

* Must remain CoreCLR compliant (see links below). Note that given the current requirements for the Docker.DotNet.X509, the project is still compiling for net46 instead of netstandard. However, once updated implementation for TLS authentication is present, the project will be updated for netstandard and expected to compile and function on Nano Server using the .NET Core CLR and Core Libraries available there.

##Compilation

To compile this project, use the dotnet CLI (https://github.com/dotnet/cli) to execute a publish command:

"dotnet publish .\\src\\Docker.PowerShell -o .\\src\\Docker.PowerShell\\bin\\Module\\Docker.PowerShell -r win"

This will produce the PowerShell module at ".\src\Docker.PowerShell\bin\Module\Docker.PowerShell" in the project folder. If Visual Studio is not already installed, the dotnet CLI may require an additional installation of the .NET 4.6 developer pack (https://www.microsoft.com/en-us/download/details.aspx?id=48136).

NOTE: This project uses Docker.DotNet as a git submodule (use "git submodule --help" to view manual pages for submodule). This requires one-time initializtion of the submodule with "git submodule init" and updating via "git submodule update" whenever the proejct targets a new commit of Docker.DotNet.

##Using Visual Studio Code

This project also includes support for Visual Studio Code (https://code.visualstudio.com/, https://github.com/Microsoft/vscode) in the .vscode folder. Using VSCode on the top-level folder, the restore, build, and test tasks will be available. Restore will perform "dotnet restore" across the whole project to reload any dependencies. Build will perform the "dotnet publish" command with the arguments listed in the compilation section above. Test will launch a new powershell window with the module loaded for manual testing.