You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The debugger used in most Microsoft owned IDEs (vsdbg) is shipped with a
restrictive license (see below). This makes it harder for other Projects to integrate
support for languages like C# or F#.
-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Considering that Visual Studio for Mac essentially is (based on) Mono
Develop, this constraint in particular does not seem fair.
My suggestion would be to move vsdbg to a permissive license like MIT
or at least allow other projects to use it.
Reacted by Angel D. Munoz, Max Katz, Oscar Polo, Muhammad Sammy, Matthias Koch, Joseph Woodward, Vabka, Tobias Hoppenthaler, Timur Zanagar, Simon Cropp and 103 more
Reacted by Sar Malik, Manoj Baishya, Philippe Parisot, José I. Escudero, inson1, Nate C. and byddha
@terrajobst since I got no response I guess this isn't the right repository to file this issue. Would be great if you could point me to the right repo or person.
Yes, but the comments went off topic pretty fast. It also never got an official answer (other than the linked one from 2017).
If Microsoft reconsiders the issue and decides that the change to a permissive license would fit it's open source image that would be great, if not at least MonoDevelop should be added to the list of allowed applications.
Having broken down the license chain, I'm going to recommend a change:
From:
"You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications."
To:
"You may only use the Microsoft .NET Core Debugger (vsdbg)
to help you develop and test your applications."
Why? Because it could be accomplished anyway by another IDE programmatically driving visual studio code, and it may be possible to completely hollow out Visual Studio for Mac because of its original derivation from monodevelop which is LGPL.
Reacted by Albert Khoroshun
Reacted by Brian Reading, Viktor Svub, Alexander Trauzzi, Jan Jones, Manoj Baishya, Romain Heller, Parvis and Albert Khoroshun
Not so much. The only (bad) news is that the hot reloading support for debugging was implemented in closed-source Dev Kit extension, not in open-source C# e extension. Looks like they have no plans to open-source neither the extenstion, nor the debugger.
I also have no idea. I can understand not making opensource some commerically profittable tools like copilot or integrations with cloud features (like azure). But the debugger is the same core compnent of "SDK" as the compiler for example. They pretend that .NET is an open-source platform but if you start using it, you will soon find that it is not true.
@Igorgro Thanks for the reply! That's disappointing, I wonder what's the intention behind not making it open source.
They've already made pretty much the whole .NET environment open source, why not the debugger?
That would be the nail in the coffin for Visual Studio. The reason there are not much alternative IDEs/Editors and we are hostages of Rider is because SOS/vsdbg isn't OSS.
Jetbrains had to implement the debugger on their own. Even for them which are a well-funded company it is a considerable amount of non-trivial work. They lag always behind and features (as of this writing, .Net 8 is not fully supported on Rider yet) and even when they "catch up", still not a comparable experience with Visual Studio.
More and more people from the .Net community (including corporate teams) are moving to use Macs (specially after Apple Silicon) and Linux as their development machines, and that means less VS licenses being sold and (because of the lack of alternative) you have to resort to Rider.
VSCode is AMAZING, but the C# extension was aways subpar (to be polite). Now that MSFT took over its development, it may get better, but don't be surprised if the features start to align with VS that they would be behind "paywall".
Don't get me wrong, I'm not against paid software, and would be willing to pay (more than already do) for it as long as it work. I'm just stating the reason most of us believe this (OSS SOS/vsdbg) would never happen.
For now, as someone that has move away from Windows to MacOS since first .Net Core release, all we can do is still be hostages of JB with Rider.
I also have no idea. I can understand not making opensource some commerically profittable tools like copilot or integrations with cloud features (like azure). But the debugger is the same core compnent of "SDK" as the compiler for example. They pretend that .NET is an open-source platform but if you start using it, you will soon find that it is not true.
I don't think .Net will ever get back to closed source. The community got too big around it.
That would be the nail in the coffin for Visual Studio. The reason there are not much alternative IDEs/Editors and we are hostages of Rider is because SOS/vsdbg isn't OSS.
Tbh, it doesn't actually need to be OSS. All we need is for this license to get relaxed allowing other products to use it, even if it requires those other products to OSS their implementation around the debugger capabilities.
As for me I also not against the paid software but only if it worths that. Being forced to pay to be able to debug software to see a unit tests list widget in my IDE (dev kit) is beyond my understanding.
What I'm against of is marking the product (.NET) with "100% open sosurce" slogan with hidden text "but components A, B and C are proprietary". This smells like fraudulent agreement with a hidden conditions. Such things don't give more respect to MS.
Reacted by Parvis , Albert Khoroshun and Mikhail Tyukin
That would be the nail in the coffin for Visual Studio
Don't see the connection with Visual Studio here. The debugger should be a part of the core sdk the same as the compiler and the runtime.
On the other hand, there is nothing wrong to make a parts of a proprietary commerical product open-source. For example GitLab have a completely open-source codebaser but this doesn't stop them from making money from it.
I understand your feeling but I can't agree 100% with you.
Javascript is fully open source. But there is no debugger attached to it nor the spec (if the JS developer actually care about debugging and not just console.log() 😄 ). V8, a javascript runtime in other hand, has the debugger/profiler protocol implemented on it. So any tool can just wrap it and provide a debugger experience.
The .Net SDK/Runtime provide ways to implement the debugger interfaces/profiles so you can inspect the runtime. That is open wide and as expected documented. The problem is that it is very complex as I said and not an easy thing to implement. That is precisely what JB did when implementing Rider's debugger. The debugger is considered tooling. If you look at C/C++ for example, you are not obligated to use GDB to debug your application. People using clang don't use it.
In other words, even though it sucks for us, users, it is not a shady thing as it is done everywhere else.
Don't see the connection with Visual Studio here. The debugger should be a part of the core sdk the same as the compiler and the runtime.
I meant to say that Visual Studio sales are not doing well according to multiple articles as people (developers) are moving away from Windows to use other things, like Macs. The only thing that people working with .Net has which forced them stay on windows, was the old .Net framework. If they moved to .Net Core ownwards, that is gone and they can use whatever they want. That directly imply that people would need an IDE/Editor on those platforms. The SOS/vsdbg uses the same closed source binaries which implement the .Net CLR interfaces for debugging used by Visual Studio.
It would be fantastic if they OSS, but, as said, I doubt it would ever happen.
On the other hand, there is nothing wrong to make a parts of a proprietary commerical product open-source. For example GitLab have a completely open-source codebaser but this doesn't stop them from making money from it.
There are multiple ways of OSS as there are multiple ways of doing business. They've just pick one.
Again, it is all sad, we could have nice new IDE/Editors being built by the community and other companies BUT, there is nothing to blame on MSFT on this one, unfortunately...
I would like to change VS code a little bit for my preferences but in that case I can't use it as a debugger for .NET. Microsoft, please make vsdbg free to use.
Reacted by Serg Takawa, malucart, byddha and Albert Khoroshun
.NET claims to be open-source, but keeping the debugger locked behind proprietary products undermines that promise. Debugging isn’t a premium feature, it’s a basic part of development. Keeping vsdbg closed is greedy and pointles; it doesn’t even scratch Microsoft’s bottom line, let alone amount to 0.00X% of your revenue. Open-sourcing it would cost nothing but would build goodwill, foster community contributions & strengthen its position in today's day and age where modern languages come with modern tooling.
On top of that, Visual Studio doesn’t even support Linux, where most .NET code is run. This forces developers to either use Rider, boosting the popularity of your biggest competitor, settle for subpar tools like VS Code, or resort to community solutions like Samsung’s netcoredbg, which pale in comparison. Open-sourcing vsdbg would finally let developers debug on whatever configuration they want without pointless restrictions.
Stop pretending .NET is open-source while holding critical tools hostage. This kind of behavior undermines everything you’ve achieved with .NET’s open-source transition. Open-sourcing vsdbg is the next logical step to align with the values Microsoft claims to stand for.
Reacted by Alexandra Marinescu, Ghost4Man, Albert Khoroshun, Vladimir Chirikov, Igor Mahov, Boros Máté, Nightowl and Michael Avagianos
Reacted by Albert Khoroshun, Wes Thomas and Michael Avagianos
FYI, I have created SharpDbg, an open source C# implementation of a .NET debugger. I primarily created it for use with SharpIDE, as netcoredbg does not support all the features necessary for a good IDE experience (eg DebuggerDisplay attribute evaluation).
Activity
JaggerJo commentedon Jun 18, 2020
@terrajobst since I got no response I guess this isn't the right repository to file this issue. Would be great if you could point me to the right repo or person.
dasMulli commentedon Jun 18, 2020
There's already an issue about this.. #505
JaggerJo commentedon Jun 18, 2020
Hey @dasMulli,
Yes, but the comments went off topic pretty fast. It also never got an official answer (other than the linked one from 2017).
If Microsoft reconsiders the issue and decides that the change to a permissive license would fit it's open source image that would be great, if not at least MonoDevelop should be added to the list of allowed applications.
vivekcek commentedon Jul 20, 2020
Give this to mono develop or provide a visual studio for linux.
joshudson commentedon Nov 27, 2020
Having broken down the license chain, I'm going to recommend a change:
From:
"You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications."
To:
"You may only use the Microsoft .NET Core Debugger (vsdbg)
to help you develop and test your applications."
Why? Because it could be accomplished anyway by another IDE programmatically driving visual studio code, and it may be possible to completely hollow out Visual Studio for Mac because of its original derivation from monodevelop which is LGPL.
xjose97x commentedon Dec 2, 2023
It's almost 2024. Are there any news regarding this?
Igorgro commentedon Dec 2, 2023
Not so much. The only (bad) news is that the hot reloading support for debugging was implemented in closed-source Dev Kit extension, not in open-source C# e extension. Looks like they have no plans to open-source neither the extenstion, nor the debugger.
xjose97x commentedon Dec 2, 2023
@Igorgro Thanks for the reply!
That's disappointing, I wonder what's the intention behind not making it open source.
They've already made pretty much the whole .NET environment open source, why not the debugger?
Igorgro commentedon Dec 2, 2023
I also have no idea. I can understand not making opensource some commerically profittable tools like copilot or integrations with cloud features (like azure). But the debugger is the same core compnent of "SDK" as the compiler for example. They pretend that .NET is an open-source platform but if you start using it, you will soon find that it is not true.
galvesribeiro commentedon Dec 2, 2023
That would be the nail in the coffin for Visual Studio. The reason there are not much alternative IDEs/Editors and we are hostages of Rider is because SOS/vsdbg isn't OSS.
Jetbrains had to implement the debugger on their own. Even for them which are a well-funded company it is a considerable amount of non-trivial work. They lag always behind and features (as of this writing, .Net 8 is not fully supported on Rider yet) and even when they "catch up", still not a comparable experience with Visual Studio.
More and more people from the .Net community (including corporate teams) are moving to use Macs (specially after Apple Silicon) and Linux as their development machines, and that means less VS licenses being sold and (because of the lack of alternative) you have to resort to Rider.
VSCode is AMAZING, but the C# extension was aways subpar (to be polite). Now that MSFT took over its development, it may get better, but don't be surprised if the features start to align with VS that they would be behind "paywall".
Don't get me wrong, I'm not against paid software, and would be willing to pay (more than already do) for it as long as it work. I'm just stating the reason most of us believe this (OSS SOS/vsdbg) would never happen.
For now, as someone that has move away from Windows to MacOS since first .Net Core release, all we can do is still be hostages of JB with Rider.
I don't think .Net will ever get back to closed source. The community got too big around it.
galvesribeiro commentedon Dec 2, 2023
Tbh, it doesn't actually need to be OSS. All we need is for this license to get relaxed allowing other products to use it, even if it requires those other products to OSS their implementation around the debugger capabilities.
Igorgro commentedon Dec 2, 2023
As for me I also not against the paid software but only if it worths that. Being forced to pay to be able to debug software to see a unit tests list widget in my IDE (dev kit) is beyond my understanding.
What I'm against of is marking the product (.NET) with "100% open sosurce" slogan with hidden text "but components A, B and C are proprietary". This smells like fraudulent agreement with a hidden conditions. Such things don't give more respect to MS.
Igorgro commentedon Dec 2, 2023
Don't see the connection with Visual Studio here. The debugger should be a part of the core sdk the same as the compiler and the runtime.
On the other hand, there is nothing wrong to make a parts of a proprietary commerical product open-source. For example GitLab have a completely open-source codebaser but this doesn't stop them from making money from it.
galvesribeiro commentedon Dec 2, 2023
I understand your feeling but I can't agree 100% with you.
Javascript is fully open source. But there is no debugger attached to it nor the spec (if the JS developer actually care about debugging and not just console.log() 😄 ). V8, a javascript runtime in other hand, has the debugger/profiler protocol implemented on it. So any tool can just wrap it and provide a debugger experience.
The .Net SDK/Runtime provide ways to implement the debugger interfaces/profiles so you can inspect the runtime. That is open wide and as expected documented. The problem is that it is very complex as I said and not an easy thing to implement. That is precisely what JB did when implementing Rider's debugger. The debugger is considered tooling. If you look at C/C++ for example, you are not obligated to use GDB to debug your application. People using clang don't use it.
In other words, even though it sucks for us, users, it is not a shady thing as it is done everywhere else.
I meant to say that Visual Studio sales are not doing well according to multiple articles as people (developers) are moving away from Windows to use other things, like Macs. The only thing that people working with .Net has which forced them stay on windows, was the old .Net framework. If they moved to .Net Core ownwards, that is gone and they can use whatever they want. That directly imply that people would need an IDE/Editor on those platforms. The SOS/vsdbg uses the same closed source binaries which implement the .Net CLR interfaces for debugging used by Visual Studio.
It would be fantastic if they OSS, but, as said, I doubt it would ever happen.
There are multiple ways of OSS as there are multiple ways of doing business. They've just pick one.
Again, it is all sad, we could have nice new IDE/Editors being built by the community and other companies BUT, there is nothing to blame on MSFT on this one, unfortunately...
KhorAMus commentedon Mar 14, 2024
I would like to change VS code a little bit for my preferences but in that case I can't use it as a debugger for .NET. Microsoft, please make vsdbg free to use.
byddha commentedon Nov 24, 2024
.NET claims to be open-source, but keeping the debugger locked behind proprietary products undermines that promise. Debugging isn’t a premium feature, it’s a basic part of development. Keeping vsdbg closed is greedy and pointles; it doesn’t even scratch Microsoft’s bottom line, let alone amount to 0.00X% of your revenue. Open-sourcing it would cost nothing but would build goodwill, foster community contributions & strengthen its position in today's day and age where modern languages come with modern tooling.
On top of that, Visual Studio doesn’t even support Linux, where most .NET code is run. This forces developers to either use Rider, boosting the popularity of your biggest competitor, settle for subpar tools like VS Code, or resort to community solutions like Samsung’s netcoredbg, which pale in comparison. Open-sourcing vsdbg would finally let developers debug on whatever configuration they want without pointless restrictions.
Stop pretending .NET is open-source while holding critical tools hostage. This kind of behavior undermines everything you’ve achieved with .NET’s open-source transition. Open-sourcing vsdbg is the next logical step to align with the values Microsoft claims to stand for.
MattParkerDev commentedon May 5, 2026
FYI, I have created SharpDbg, an open source C# implementation of a .NET debugger. I primarily created it for use with SharpIDE, as netcoredbg does not support all the features necessary for a good IDE experience (eg DebuggerDisplay attribute evaluation).