From 0c787bc0820c819bfdaf707915dfb718423c588a Mon Sep 17 00:00:00 2001 From: Sumit Ghosh <13281246+sughosneo@users.noreply.github.com> Date: Wed, 10 Feb 2021 18:31:52 +0530 Subject: [PATCH] Updated VS --- Docker-host.md | 2 +- Windows-setup.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Docker-host.md b/Docker-host.md index f2bbe7f..214e56b 100644 --- a/Docker-host.md +++ b/Docker-host.md @@ -2,7 +2,7 @@ _IMPORTANT: This instructions section is in early draft state because the current version of eShopOnContainers has been tested mostly on plain Docker engine and just smoke tests on some orchestrators like AKS and Kubernetes._ -However, since there are a few folks testing it in "production" environments, out of the dev PC machine (VS2017+Docker) but in a prod. environment like Azure or a regular Docker Host, here's some important information to consider, in addition to the [CLI setup procedure detailed for Windows](Windows-setup). +However, since there are a few folks testing it in "production" environments, out of the dev PC machine (VS2019+Docker) but in a prod. environment like Azure or a regular Docker Host, here's some important information to consider, in addition to the [CLI setup procedure detailed for Windows](Windows-setup). The "by default configuration" in the `docker-compose.override.yml` file is set with specific config so it makes it very straightforward to test the solution in a Windows PC with Visual Studio or the CLI, almost just F5 after the first configuration. But, for instance, it is using the "**10.0.75.1**" IP used by default in all "Docker for Windows" installations, so it can be used by the Identity Container for the login page when being redirected from the client apps **without you having to change any specific external IP**, etc. diff --git a/Windows-setup.md b/Windows-setup.md index 09005cc..ba997de 100644 --- a/Windows-setup.md +++ b/Windows-setup.md @@ -210,7 +210,7 @@ At this point, after waiting sometime for the NuGet packages to be properly rest ![](images/Windows-setup/debug-F5-button.png) -VS 2017 should compile the .NET projects, then create the Docker images and finally deploy the containers in the Docker host (your by default Linux VM in Docker for Windows). +VS 2019 should compile the .NET projects, then create the Docker images and finally deploy the containers in the Docker host (your by default Linux VM in Docker for Windows). Note that the first time you hit F5 it'll take more time, a few minutes at least, because in addition to compile your bits, it needs to pull/download the base images (SQL for Linux Docker Image, Redis Image, ASPNET image, etc.) and register them in the local image repo of your PC. The next time you hit F5 it'll be much faster. Finally, because the docker-compose configuration project is configured to open the MVC application, it should open your by default browser and show the MVC application with data coming from the microservices/containers: