From c650dda90053ed1b7618e529e3ab227bc1f3554c Mon Sep 17 00:00:00 2001 From: Levi Rocha Date: Tue, 7 Apr 2020 15:50:00 -0400 Subject: [PATCH] Fix typos --- .../docker-app-development-workflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md b/docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md index 33893705367e3..b8d38fb3398ef 100644 --- a/docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md +++ b/docs/architecture/microservices/docker-application-development-process/docker-app-development-workflow.md @@ -280,7 +280,7 @@ The resulting file is then: 7 COPY . . 8 RUN dotnet restore /ignoreprojectextensions:.dcproj 9 WORKDIR /src/src/Services/Catalog/Catalog.API -10 RUN dotnet publish Catalog.API.csproj -c Release -0 /app +10 RUN dotnet publish Catalog.API.csproj -c Release -o /app 11 12 FROM base AS final 13 WORKDIR /app @@ -473,7 +473,7 @@ After the docker-compose up command runs, the application and its related contai #### Using Visual Studio -Running a multi-container application using Visual Studio 2019 can't get any simpler. You just press **Ctrl-F5** to run or **F5** to debug, as usual, setting up the **docker-compose** project as the startup project. Visual Studio handles all needed setup, so you can create breakpoints as usual and debug what finally become independent processes running in "remote servers", with the debugger already attached. just like that. +Running a multi-container application using Visual Studio 2019 can't get any simpler. You just press **Ctrl-F5** to run or **F5** to debug, as usual, setting up the **docker-compose** project as the startup project. Visual Studio handles all needed setup, so you can create breakpoints as usual and debug what finally become independent processes running in "remote servers", with the debugger already attached, just like that. As mentioned before, each time you add Docker solution support to a project within a solution, that project is configured in the global (solution-level) docker-compose.yml file, which lets you run or debug the whole solution at once. Visual Studio will start one container for each project that has Docker solution support enabled, and perform all the internal steps for you (dotnet publish, docker build, etc.).