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

Make dotnet debug launch config independent of the framework version number #5505

Closed
fpintos opened this issue Dec 23, 2022 · 1 comment
Closed

Comments

@fpintos
Copy link

fpintos commented Dec 23, 2022

Is your feature request related to a problem? Please describe.

When we create a dotnet program with vscode, for example, following https://learn.microsoft.com/en-us/dotnet/core/tutorials/with-visual-studio-code, we end up with a launch.json file that has the framework version hardcoded. For example, it says:
"program": "${workspaceFolder}/bin/Debug/net7.0/myApp.dll",

If someone on the team updates the version of the framework that is used by the application and forgets to update the launch.json file, other developers end up with a broken F5-debug experience. This has happened in our project multiple times, as we moved from 3.0 to 5.0, then to 6.0 and now to 7.0.

Describe the solution you would like

Make the setting in launch.json version independent by default.
The debug launcher could try to figure out the folder where the application was built, and launch from there by default.
For example, maybe the configuration should say something like:
“program”: “${debugOutput}/${assemblyName}.dll”

Applicable Scenarios

Debugging dotnet applications in Visual Studio Code.

@gregg-miskelly
Copy link
Contributor

I don't think we will do exactly what you are suggesting here, but we do have plans to hopefully move launch.json to specifying a project to launch rather than program, which would solve the issue you are getting at. There is a very old work item to track this (#1876), but hopefully we aren't quite as far from working on this as the age of this work item might imply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants