Skip to content

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

Open
sliceofbytes opened this issue Sep 26, 2023 · 15 comments
Open

C# Debugging does not work. #956

sliceofbytes opened this issue Sep 26, 2023 · 15 comments

Comments

@sliceofbytes
Copy link

  1. Unable to start debugging. .NET Debugging is supported only in Microsoft versions of VS Code
  2. Windows 11
  3. Attempt to build any C# solution with vsdbg.exe in cursor.

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.

@xcellenceit
Copy link

Exactly, this would be very much required for c# developers.

@truell20
Copy link
Contributor

truell20 commented Oct 6, 2023

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?

@jeganathpv
Copy link

Though C# Dev kit extension working fine in cursor. Debugging is still a challenge. This should be prioritise at least before August 2024 as VS for Mac is planned to retire and Cursor would be the complete option for the migration.
image

@cannonmaster
Copy link

Does any update on this?

@jeganathpv
Copy link

Seems like Microsoft forcefully blocked other fork apps of VS Code

@superkeka
Copy link

Does any update on this?

Fix: VSCodium/vscodium#82 (comment)

@calzakk
Copy link

calzakk commented Sep 28, 2024

Does any update on this?

Fix: VSCodium/vscodium#82 (comment)

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.

@fazedordecodigo
Copy link

Any solution to this problem?

@garfbradaz
Copy link

This issue has been open since 2016, so guessing this isnt being fixed anytime soon.

dotnet/vscode-csharp#1059

@garfbradaz
Copy link

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?

Samsung have created their own?

https://github.com/Samsung/netcoredbg?tab=readme-ov-file

@alex-jitbit
Copy link

Some updates in the linked MS issue: dotnet/vscode-csharp#1059 (comment)

Update: .NET team is working on extracting the debugging structure from the licensed debugger dll. Search 'cDAC' in the issues of dotnet runtime repo

@jinweihuang20
Copy link

same issue.

@gsferreira
Copy link

I documented here how I worked around this limitation using Samsung/netcoredbg.
It might be useful:
https://guiferreira.me/archive/2025/how-to-debug-dotnet-code-in-cursor-ai/

@EvenC-tw
Copy link

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.

@harindaka
Copy link

harindaka commented Mar 26, 2025

Anyone got netcoredbg working within a linux based docker container while debugging with cursor in the host machine?

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

No branches or pull requests