Closed marcfreiheit closed 6 years ago
@marcfreiheit What do you get when you run docker exec -i local_cablereelservice_1 ~/vsdbg/vsdbg --interpreter=vscode
from a terminal?
Hey @gregg-miskelly, I'm getting this error: oci runtime error: exec failed: container_linux.go:265: starting container process caused "exec: \"/Users/marc/vsdbg/vsdbg\":stat /Users/marc/vsdbg/vsdbg: no such file or directory"
.
Fixed that by setting an absolute path in launch.json. Debugger starts and seems to trigger on breakpoints, but now I'm getting the following error: Unable to open 'HomeModule.cs': File not found (file:///app/src/modules/HomeModule.cs).
Btw, is there a way to enable debug or log messages in launch.json?
Currently the pipe transport handler will do a good job of reporting errors logged to stderr, but if the pipe program logs errors of stdout we silently drop them on the floor. I will retitle this to investigate doing a better job here.
Great and thanks! When can I make use of the new debugging capabilities? (:
We are aiming to release 1.14 pretty soon. But you can try it now if you like -- https://github.com/OmniSharp/omnisharp-vscode/wiki/Installing-Beta-Releases
Environment data
dotnet --info
output:VS Code version: Version 1.18.0 (1.18.0) C# Extension version: 1.13.0
Goal
I would like to create a .Net Core application based on multiple microservices. The services should be developed and published with Docker. The development process should be as comfortable as possible, without waiting minutes for Docker to build images and run the .Net app. Therefore, I'm mounting my source code inside the docker container and started the
dotnet watch run -p /app
command in order to restart the server on code changes. That's working well. Only downside is that I have to put my source code into a subfolder to not mountbin/
andobj/
folder, because the container is building the app and not my host machine. If you got improvements or ideas, please let me know! I'm still learning Docker and .Net Core, therefore I'm happy to get feedback!Now I would like to debug my code inside the docker container.
Steps to reproduce
Dockerfile
Compose
launch.json
Project Strutcure
All microservices are hosted inside one repo. They should follow a structure similar the following one:
Expected behavior
Actual behavior
Output:
and:
I have no clue what is going wrong and I don't get any valuable from the output and error message. I've tried selecting every process from the vs picker (
${command:pickRemoteProcess}
) without success. Any ideas or suggestions? Thanks in advance!