C# Debugging does not work.

[sliceofbytes]

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]

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

[truell20]

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]

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.

[cannonmaster]

Does any update on this?

[jeganathpv]

Seems like Microsoft forcefully blocked other fork apps of VS Code

[superkeka]

Does any update on this?

Fix: https://github.com/VSCodium/vscodium/issues/82#issue-409806641

[calzakk]

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]

Any solution to this problem?

[garfbradaz]

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

https://github.com/dotnet/vscode-csharp/issues/1059

[garfbradaz]

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]

Some updates in the linked MS issue: https://github.com/dotnet/vscode-csharp/issues/1059#issuecomment-2629597937

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]

same issue.

[gsferreira]

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]

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]

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

[alex-jitbit]

Looks like Cursor's fork of C# extension now supports debugging (via netcoredbg)

https://forum.cursor.com/t/when-are-you-adding-net-debugging/38517/9?u=alex-jitbit

Looks like it works. Just tested on a mac.

[MRL-00]

This issue can be closed. :)

[alex-jitbit]

Yeah, except that C# extension is entirely abandoned.

[MRL-00]

Sorry @alex-jitbit you are correct. Looks like there is also no coms from Cursor on this. Would be good to know what their plans are with this extension. @truell20