Updated 02. Setting eShopOnContainers in a Visual Studio 2017 environment (markdown)
parent
681af74b57
commit
9dca5363b4
@ -17,18 +17,17 @@ For further instructions, especially if this is the first time you are going to
|
||||
---------------------------------------------------------------------------------
|
||||
|
||||
## Detailed procedure: Setting eShopOnContainers up in a Visual Studio 2017 development machine
|
||||
Visual Studio 2017 with its built-in Docker Tools adds a number of very convenient features which are solid reasons why you'd want to use VS 2017 when developing Docker container based applications. The most important features are:
|
||||
Visual Studio 2017 provides built-in Docker Tools with features like:
|
||||
* Docker-compose support
|
||||
* Multi-container debugging, supporting true microservice scenarios
|
||||
* Windows Server Containers for .NET Framework apps
|
||||
* Addition of CI build definition using a docker-compose.ci.build.yml file at the solution level.
|
||||
* Configure Continuous Integration experience for setting up CI/CD with VSTS to Azure Container Services
|
||||
* Linux Docker Containers (usually, for .NET Core apps)
|
||||
* Windows Docker Containers (usually for .NET Framework apps)
|
||||
|
||||
Being the first one (Multi-container debugging, supporting true microservice scenarios) the most loved feature, probably.
|
||||
So, here's how to setup a VS 2017 environment where you can test eShopOnContainers.
|
||||
|
||||
### GitHub branch to use
|
||||
By default, use the DEV branch which has the latest changes and testing.
|
||||
The MASTER branch is also an option but it'll usually be less up to date while keep evolving the application.
|
||||
The MASTER branch is also an option but it'll usually be less up to date while we keep evolving the application.
|
||||
|
||||
### Software requirements
|
||||
Software installation requirements for a Windows dev machine with Visual Studio 2017 and Docker for Windows:
|
||||
|
Loading…
x
Reference in New Issue
Block a user