Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Docker files for .NET Core does not automatically generate .NET debug assets #2669

Closed
ucheNkadiCode opened this issue Jan 25, 2021 · 3 comments · Fixed by #2680
Closed

Comments

@ucheNkadiCode
Copy link
Contributor

Context: dotnet/vscode-csharp#3403
Merged PR: dotnet/vscode-csharp#4241

When a user adds .NET Core Dockerfiles to Workspace, in order to F5 a project successfully, they need to add the .NET Core build/debug assets before adding Docker debug assets (either via "Add Docker Files..." or "Initialize for debugging", due to dotnet/vscode-csharp#3403 (overwriting the existing launch and task files) which has now been fixed.

Could we create functionality that automatically runs this command in the background for a smoother F5 experience?

@bwateratmsft
Copy link
Contributor

🤦‍♂️ I only just realized, the change in the C# extension isn't released just yet. Naturally we need to wait until the fix is (widely-enough) available before we proceed--probably will need to be moved to 1.11.0 but I'll leave it in 1.10.0 for now.

@ucheNkadiCode, can you follow up with the C# folks and see when they expect to release next?

@bwateratmsft
Copy link
Contributor

Moving to 1.11.0 so we can give time for users to upgrade to the needed C# extension version.

@bwateratmsft bwateratmsft modified the milestones: 1.10.0, 1.11.0 Jan 28, 2021
@bwateratmsft bwateratmsft added P1 and removed P2 labels Jan 28, 2021
@bwateratmsft bwateratmsft removed their assignment Mar 2, 2021
@bwateratmsft
Copy link
Contributor

This is now released in Docker extension version 1.11.0.

@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants