Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,577 questions
Dockerized ASP.NET apps no longer starting from Visual Studio
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 95%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJK%3C/text%3E%3C/svg%3E)
John K
6
Reputation points
I have two containerized ASP.NET applications in a single VS2019 solution, that I usually run using docker-compose via Visual Studios integrated tools. I'm starting them either without debugger (using CTRL+F5), or with debugger (using just F5). This setup has worked for a couple of years now. But a few days ago, all of a sudden, the applications aren't starting up anymore when I try to start them from Visual Studio. The containers are being build, but the Container Tools output just says "========== Launching ==========" and then nothing. And the logs from both of the started containers are empty.
I'm not sure if this has anything to do with the fact that VS will add some overrides to the docker-compose file (like "ENTRYPOINT tail -f /dev/null") but then again, it has always worked until now, so I don't know why this would suddenly start working.
I can still start up the applications from a terminal using the docker-compose CLI. However Visual Studio can't seem to attach a debugger to it if I run the containers that way, so I really need to get Visual Studio working again.
I can only think of three factors that may cause this:
- A change in my own code
- A bug in the latest VS2019 update
- A change in the latest Docker Desktop (Windows) update
I've eliminated number 1 by checking out an old version of my source code, but that didn't help.
I've eliminated number 2 by installing an older version of VS2019 Professional, but that also didn't help.
Has anyone else had any issues with this lately?
Visual Studio
Visual Studio Debugging
Visual Studio Debugging
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Debugging: The act or process of detecting, locating, and correcting logical or syntactical errors in a program or malfunctions in hardware. In hardware contexts, the term troubleshoot is the term more frequently used, especially if the problem is major.
935 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 47%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
PengGe-MSFT 3,326 Reputation points2021-11-09T08:17:09.47+00:00 Hi @John K
Could you tell me your visual studio's version. Will you encounter the same problem if you create a new project?
According to your description:I've eliminated number 2 by installing an older version of VS2019 Professional, but that also didn't help.
Will you encounter this issue in the old version of Visual Studio?
-
John K 6 Reputation points
2021-11-09T08:18:39.737+00:00 Well, are you sure the problem is with Docker Tools and not with Visual Studio? How can you tell?
-
John K 6 Reputation points
2021-11-09T11:52:50.907+00:00 I just found the problem. It turned out this portion was missing from the launchSettings.json:
"Docker": { "commandName": "Docker", "launchBrowser": true, "launchUrl": "{Scheme}://{ServiceHost}:{ServicePort}", "publishAllPorts": true }Strangly enough, I just needed to add it back to ONE of the applications, and now both get started through docker-compose by VS.
So, error on my part, sorry but thanks anyway!
Sign in to comment