-
Notifications
You must be signed in to change notification settings - Fork 1.9k
C# Debugging does not work. #956
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
Comments
Exactly, this would be very much required for c# developers. |
Would certainly like to get a good C# debugging experience working in Cursor. Perhaps there's an open source solution that we could try to build-on or support? |
Does any update on this? |
Seems like Microsoft forcefully blocked other fork apps of VS Code |
|
Seems that's a workaround, not a fix, if you want to use Microsoft's debugger (vsdbg). Disappointing that this is still an issue after a year, but I guess the blame lies with Microsoft. |
Any solution to this problem? |
This issue has been open since 2016, so guessing this isnt being fixed anytime soon. |
Samsung have created their own? https://github.com/Samsung/netcoredbg?tab=readme-ov-file |
Some updates in the linked MS issue: dotnet/vscode-csharp#1059 (comment)
|
same issue. |
I documented here how I worked around this limitation using Samsung/netcoredbg. |
Currently, I am temporarily using the method provided by gsferreira, and I have not encountered any unsolvable issues. However, as a web developer, I need to specifically add the "ASPNETCORE_URLS" property to properly expose https in the development environment. |
Anyone got netcoredbg working within a linux based docker container while debugging with cursor in the host machine? |
Any work arounds or plans to resolve this? I do a ton of C# programming but quite a context shift to have to open another app anytime I want to build / debug.
The text was updated successfully, but these errors were encountered: