ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated Setting the eShopOnContainers solution up in a hybrid VS2017 CLI environment (markdown)

Cesar De la Torre 2017-02-19 19:43:15 -08:00
parent 607634b02b
commit b333b948b3
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Setting-the-eShopOnContainers-solution-up-in-a-hybrid-VS2017---CLI-environment.md

@ -1,4 +1,9 @@
This environment means that you might want to build/run/debug the solution through VS 2017 or other times you might want to build/run by using the CLI (Command line interface plus PowerShell scripts and "docker-compose up/build" CLI).
This environment is a mix between the VS 2017 environment and a Windows CLI environment. Therefore, in this case sometimes you might want to build/run/debug the solution through VS 2017 and other times you might want to build/run by using the CLI (Command line interface plus PowerShell scripts and "docker-compose up/build" CLI).
Because in this environment you need to build the .NET projects from the dotnet CLI plus being able to build the docker images with docker-compose build, there are some SDKs that need to be available from the command line and you need to install them or configute them so commands are available from the cmd context.
In regards the required SDK installation for using the CLI, you need first to follow the same steps than the ones specified in the CLI setup, here:
https://github.com/dotnet/eShopOnContainers/wiki/Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code)
However, there are few additional steps to be performed so the VS 2017 configuration matches the CLI configuration and you don't have conflicts.
VS config about external NODE/NPM path, etc....