You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@galvesribeiro, Good question. The yo docker experience is definitely out of date. We currently don't have any guidance on this. Let me dig around a little and see what I can come up with.
Thanks @MichaelSimons I appreciate that. I'm struggling to get it to work here. Even if I use VS2017 which has that Add Docker Support function, it works, but there is no docs on how that works whatsoever so I can't try reproduce it on VSCode. Looking forward to hear from you, thanks!
I moved this to microsoft/generator-docker#130 since the underlying issue is not specific to the Docker image rather it is with the broken yo docker experience.
@MichaelSimons most of the fuss is about downloading clrdbg into the containers. Does it make sense to create a public image that already includes the correct debugger? (e.g. microsoft/dotnet:1.1-sdk-msbuild-debug).
@dasMulli if you look at simple apps with a single container yes, people don't know that the SDK doesn't come with the debugger. However, when you have multiple containers (i.e. docker-compose based projects) the problem goes far from just that. Look at the new issue @MichaelSimons just created.
Activity
MichaelSimons commentedon Jan 27, 2017
@galvesribeiro, Good question. The
yo dockerexperience is definitely out of date. We currently don't have any guidance on this. Let me dig around a little and see what I can come up with.galvesribeiro commentedon Jan 27, 2017
Thanks @MichaelSimons I appreciate that. I'm struggling to get it to work here. Even if I use VS2017 which has that
Add Docker Supportfunction, it works, but there is no docs on how that works whatsoever so I can't try reproduce it on VSCode. Looking forward to hear from you, thanks!MichaelSimons commentedon Jan 27, 2017
For my own exercise, I went through the
yo dockerexperience. Even though it was out of date, I was able to get it working with a few tweaks.mkdir DockerDebugAppcd DockerDebugAppdotnet new -t Console1.1yo docker(used defaults)a.
microsoft/dotnet:1.1-sdk-msbuildb.
microsoft/dotnet:1.1-runtimea.
netcoreapp1.1dotnet restore -r debian.8-x64galvesribeiro commentedon Jan 27, 2017
Was about to ping you... I did similar thing and it work :)
However, that is not close to what we have with VS2017, where you can run/debug multiple projects using the solution-level docker-compose files...
MichaelSimons commentedon Jan 31, 2017
I moved this to microsoft/generator-docker#130 since the underlying issue is not specific to the Docker image rather it is with the broken yo docker experience.
dasMulli commentedon Jan 31, 2017
@MichaelSimons most of the fuss is about downloading clrdbg into the containers. Does it make sense to create a public image that already includes the correct debugger? (e.g.
microsoft/dotnet:1.1-sdk-msbuild-debug).galvesribeiro commentedon Jan 31, 2017
@dasMulli if you look at simple apps with a single container yes, people don't know that the SDK doesn't come with the debugger. However, when you have multiple containers (i.e. docker-compose based projects) the problem goes far from just that. Look at the new issue @MichaelSimons just created.