Description
openedon Feb 16, 2017
I was under the impression that being as open-source as possible was one of Microsoft's chief goals with .NET Core. It's very surprising then to find that the licensing for Microsoft.VisualStudio.clrdbg - the only publicly available package that exposes the .NET Core debugging API - is so restrictive:
You may only use the .NET Core Debugger Components with Visual Studio Code, Visual Studio or Xamarin Studio software to help you develop and test your applications.
Because of this restriction, JetBrains have been forced to drop debugging support for .NET Core-based projects in the latest version of Rider EAP (EAP 17) which they released today. As a company that undertakes a great deal of innovation, I am sure that there are many people at Microsoft who are saddened by the idea of a very promising application being driven backwards due to legal/licensing reasons rather than technical issues.
The lack of debugging support for .NET Core projects in the latest version of Rider is a deal-breaker for me and I'm sure many others. I would like to know:
- Why is such a restrictive license necessary in the first place when the rest of .NET Core is open-source?
- Would it be possible to lift this restriction or at least consider making exceptions for certain products like Rider?