![]() But since I am using Docker, I must select the connection target, which is the name of the container, and the process, which is “dotnet”. That opens a dialog where I can select the process. Whenever I want to debug, I simply attach the Visual Studio to the process of the project (Ctrl+Alt+P). Not to mention that I would not hit random breakpoints I’ve added and forgot to disable. I prefer to do that because it gives me the feeling that I am running closer to a real application. So, I did my usual: Start the project without debugging (Ctrl+F5). ![]() Anyway, here is the result so far:įrom that point I just wanted to see if what would happen when I run the project. Perhaps the best option is to “dockerize” a project after it’s been created. The result was a couple of duplicated files that I ended up deleting later. I decided to do both since I was just playing around. ![]() …or create a “dockerized” project from scratch. In case you don’t know, you can “dockerize” existing projects… But I ended up running into problems which resulted in a small thread on Twitter that I am expanding here.Įverything started when I decided to use Visual Studio 2019 to take care of Docker for me. ![]() You know, just to make sure that I understood everything well. I’ve been reading about Docker for a couple of weeks already and, few days ago, I decided to create a small proof of concept. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |