The Rough History of .NET Core Debuggers

August 14, 2019
Copyright © Lex Li. Maison des étudiants - Pavillion E , ETS.

There are several .NET Core debuggers out there from different vendors, and this post covers the major ones and their stories.

.NET Core Debugger from Microsoft, aka vsdbg

.NET Core was born with a debugger, of course from Microsoft, called vsdbg. With a long history and reputation in Windows based debuggers, it is not difficult for Microsoft to create such a tool on Windows, and also make it cross platform for macOS and Linux. Naturally, this debugger is a core asset for .NET Core development and also part of Visual Studio (Windows/Mac) and Visual Studio Code.

vsdbg is not open sourced and not everyone paid enough attention to the licensing terms of vsdbg (and its various components), until one day JetBrains entered the arena and shipped its .NET IDE called Rider.

.NET Core Debugger from JetBrains

It was in February 2017 that JetBrains realized the the debugging functionality of Rider was built upon a Microsoft NuGet package Microsoft.VisualStudio.clrdbg which in fact was not licensed to any third party IDEs like Rider.

Microsoft soon pulled that package out of to avoid further confusion, and JetBrains disabled .NET Core debugging in Rider EAP 17.

Luckily JetBrains was also famous for its technical excellence, so the engineers were able to write its own Windows side .NET Core debugger in just a week in EAP 18. Mac and Linux support came after about 4 months, in EAP 23.

Since then, JetBrains has been able to continuously refine its own .NET Core debugger to implement more features. Recent achievements include but are not limited to,

However, JetBrains .NET Core debugger is also proprietary, so only ships as part of the commercial IDE, Rider.

Samsung .NET Core Debugger, aka netcoredbg

Samsung joined .NET Foundation Technical Steering Group back in June 27, 2016.

That’s an important move for this hardware centric company where it embraces Microsoft .NET Core technologies to help boost its Tizen operating system.

On November 16, 2016, Visual Studio Tools for Tizen was released, and Samsung open sourced its [].NET Core debugger]( (not only for Tizen, but also for other operating systems like Windows/Mac/Linux) on GitHub.

Compared to the debuggers from Microsoft/JetBrains, this open source debugger lacks of many important features, but as the solely free tool without licensing problems it enables all kind of possibilities.

Sidenote on MonoDevelop

Visual Studio for Mac is built upon MonoDevelop. However, Microsoft does not license vsdbg to be used in MonoDevelop. That’s why earlier this year I finished the extension to enable .NET Core debugging in MonoDevelop with the Samsung debugger.

There was a long inactive period on Samsung .NET Core debugger repo since April 2019 but later the project started to be active again.

Look for other interesting posts like this one? You can visit the index page.