search

dotnet / vscode-csharp

Official C# support for Visual Studio Code
MIT License
2.85k stars 667 forks source link

Using or license vsdbg outside of VSCode #1059

Open danwalmsley opened 7 years ago

danwalmsley commented 7 years ago

Hi,

Quick question, iv noticed a fairly well known company that is developing .net ide are using your clrdbg.exe.

I run an open source project AvalonStudio (https://github.com/VitalElement/AvalonStudio/) which is mainly for c/c++ but we have started to add c# and .net support. We had a look at clrdbg and notice it prints a message to say its not available for use outside vscode, xamarin studio or visual studio.

which is why we haven't used it.

We are interested if like the company that are using it, we could get permission to use it also (we are not a company or profitable organization).

I spoke to some of the omnisharp guys and they told me @gregg-miskelly might be able to help me?

Thanks in advance for any information

DustinCampbell commented 7 years ago

To be clear, the "omnisharp guys" was me. :smile: That said, while I work for Microsoft, I'm not on the debugger team, so I recommended that @danwalmsley touch base with you.

gregg-miskelly commented 7 years ago

@danwalmsley your question is a good one, but it is above my pay grade :). I will forward it along to others to see what can be done. However, lots of people are on vacation, so it may be a little while before they respond. But if no one gets back to you by ~January 6th, please ping me.

andysterland commented 7 years ago

hi there @danwalmsley, you’re correct that the terms of clrdbg don't allow use outside of VS, VS Code, and Xamarin Studio. I’m not familiar with Avalon Studio, so if you have some time for a call it would be great to understand more about the project and where you want to go with it. You can find time on my calendar at https://calendly.com/andster. Thanks!

danwalmsley commented 7 years ago

@andysterland Thanks, that will be great I will book that in :)

How will we communicate skype?

Avalon Studio is an open source IDE project I have been running for a couple of years. More info here, but I will be happy to tell you all about it and where I want to take the project, https://github.com/VitalElement/AvalonStudio/

DustinCampbell commented 7 years ago

Did conversation already happen? Do we still need this issue or can it be closed?

dasMulli commented 7 years ago

Apparently, JetBrains Rider also hit the license issue and removed CoreCLR debugging: https://blog.jetbrains.com/dotnet/2017/02/15/rider-eap-17-nuget-unit-testing-build-debugging/

danwalmsley commented 7 years ago

@DustinCampbell yes, but still awaiting to hear back.

In case the internal discussion is going on, it might be worth pointing out that apples swift language they have https://github.com/apple/swift-lldb

open lldb debugger support. This is something that arguably should be part of c# community.

vintzl commented 5 years ago

@andysterland More than 2 years later, can you provide us any news?

Rom1deTroyes commented 1 year ago

This morning, I wanted to edit some dotnet/Blazor code to lean how to develop an UI application for a python API I'm working on.

As a vim user on GNU/Linux (I use #neovim BTW), I started to search for an LSP and a debugger, and... well, now I'm here.

Any fresh news ?

Does the M.I.T. license applied to the code in this repo is enough to build the extension, and use it in an other editor, or does the /RuntimeLicenses/ forbids that usage ?

gregg-miskelly commented 1 year ago

Two notes in case these are useful:

616b2f commented 1 year ago

Why even bother just use: https://github.com/Samsung/netcoredbg it speaks the same protocol (DAP) so if they ever decide to make vsdbg open for anyone then you just switch the binary and it's done, till then use "netcoredbg" it's pretty stable and I had never issues with it.

Rom1deTroyes commented 1 year ago 
* All of the source code in this repo is under an MIT license. The runtime license only governs the built VS Code extension as that is what includes vsdbg.

Nice disambiguation, thanx 🥇 : that was what I expected, but I was unsure of my comprehension.

* Blazor-wasm debugging is not based on vsdbg. I am not familiar enough with the scenario to comment deeply on what is or is not possible.

I'm not familiar enough with all the dotnet ecosystem to know what goes in which category, but working with spaghetti code, I put breakpoints all over the place and observe what is going on for now :-)

Why even bother just use: [...] "netcoredbg" it's pretty stable and I had never issues with it.

That is the one proposed by my LSP manager for .Net and C# so it is the one I use at the moment, without issue 👍

lawrence-laz commented 11 months ago

I just want to emphasise that even though netcoredbg is a valid workaround for now, the need for vsdbg outside of VS ecosystems is still very much desired. 🙏

Anyone who has debugged reflection heavy code or used some more complex expressions must have hit the limits of netcoredbg most probably in a form of SyntaxKindNotImplementedException.

C# and .NET are great, but for someone who use non-VS-family editors it can get pretty uncomfortable and the most disheartening part is that the solution is right here, but cannot be used due to some arbitrary fence.