Current state C# .NET debugging in VSCodium (C# extension)

baconsplit commented 3 months ago

Describe the bug Cannot debug C# .NET applications in VSCodium via the Microsoft C# extension. There exists a 2 year old issue in this repo, but I wanted to ask on the current situation. Back then, and currently in the docs, a possible workaround is to use netcoredbg from Samsung. Are there any new alternatives/workarounds?

Please confirm that this problem is VSCodium-specific

[x] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

[x] I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior: Try to debug a C# .NET application in VSCodium.

Expected behavior The debugging session begins.

Screenshots

Desktop (please complete the following information):

OS: Windows 10 64bit
Version: 10.0.19045 Build 19045

Additional context No real issue, I know. But I still hope for some help :)

tadghh commented 3 months ago

edit the debugging extension and patch out the check

YogiCoder8888 commented 1 month ago

edit the debugging extension and patch out the check

Could you please provide details on how this can be done.

Thank you.

tadghh commented 1 month ago

edit the debugging extension and patch out the check

Could you please provide details on how this can be done.

Thank you. Google "WSL run under VScodium". The snswer is on a github issues page. You would need to repatch for any non cached docker images

VSCodium / vscodium

Current state C# .NET debugging in VSCodium (C# extension) #1829