It seems we have it the worst since we can’t debug a form of VSCode… Or does that not affect you that much ?
1 Like
I think it’s difficult to solve, because the dotnet debugger is not open-source, and it is only used on vscode.
1 Like
seems I am the only one using .NET anyways… im old
1 Like
Bro, I’m here.
I worked around this on a mac using netcoredbg. It was a little bit tricky since the debugger on their repository for arm mac did not work on my machine. Compiling it from source has allowed me to debug and stop at breakpoints. You may not need to build and compile from source if you are on windows, linux or an intel mac.
Try following the readme in the repo below and let me know how that goes!
I’m a .Net developer, too. Using Laravel for some MVP stuff as well.
Laravel is faster and more supported in Cursor for now, but I get around building and expanding my first .NET project in it by using VSCode to run the code, and Cursor to change it.
Not ideal but doable.
I managed to use my 50 free premium requests from sign up just going back and forth with chat to get a .net debugger worker in the IDE itself 
I’ve been trying to get the netcoredbg working on a windows machine, have it compiled as an exe etc - now it’s throwing errors for missing DLLs. Ready to give up… not paying for Premium to use all my tokens just trying to get set up.