From 58446969544de1dc56e577e050fe87c948e093cf Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Wed, 22 Mar 2017 16:37:28 -0700 Subject: [PATCH] Updated 02. Setting eShopOnContainer solution up in a Visual Studio 2017 environment (markdown) --- ...Container-solution-up-in-a-Visual-Studio-2017-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md index a9114fe..c9f8280 100644 --- a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md +++ b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md @@ -131,7 +131,7 @@ Come back to this point when you finished with the "Setting the SPA up" process. #### Build and run eShopOnContainers from Visual Studio 2017 ##### Set docker-compose as the default StartUp project -**IMPORTANT**: If the docker-compose" project is not your "by default startup project", right click on the "docker-compose" node and select the "Set as Startup Project" menu option, as shown below: +**IMPORTANT**: If the **"docker-compose" project** is not your "by default startup project", right click on the "docker-compose" node and select the "Set as Startup Project" menu option, as shown below: At this point, after waiting sometime for the Nuget packages to be properly restored, you should be able to build the whole solution or even directly deploy/debug it into Docker by simple hitting F5 or pressing the debug "Play" button that now should be labeled as "Docker":