de4dot is an open source (GPLv3) .NET deobfuscator and unpacker written in C#. It will try its best to restore a packed and obfuscated assembly to almost the original assembly. Most of the obfuscation can be completely restored (eg. string encryption), but symbol renaming is impossible to restore since the original names aren't (usually) part of the obfuscated assembly. 

Supported obfuscators/packers

• Agile.NET (aka CliSecure)
• Babel.NET
• CodeFort
• CodeVeil
• CodeWall
• CryptoObfuscator
• DeepSea Obfuscator
• Dotfuscator
• .NET Reactor
• Eazfuscator.NET
• Goliath.NET
• ILProtector
• MaxtoCode
• MPRESS
• Rummage
• Skater.NET
• SmartAssembly
• Spices.Net
• Xenocode 

• Fixed: Android SDK not found after upgrade to 16.2
• Fixed: VS won't start after update with message tht setup is complete.
• Fixed an issue resulting in an installer verification or manifest verification fail when user is updating through the setup UI.
• Fixed an issue that caused Visual Studio to crash or stop responding during shutdown.
• Fixed a timing-related issue while saving changed Xamarin.Android project properties or building the project that resulted in the product to stop responding.
• Fixed an issue with Visual Studio crashing when C# users typed above a namespace.
• Fixed an issue preventing SSIS packages from successfully running in some circumstances after reloading a solution. 

Xamarin Versus .NET MAUI. Though .NET MAUI is the evolution of… 

IdentityServer 5 has been released This is the first major release under the new company’s banner, and here’s to many more. 

The new release, even though still considered beta, is believed to be much more stable and production ready than the widely-used 3.0.3. 

The C# language itself has changed little in version 6, the main importance of the release being the introduction of the Roslyn .NET Compiler Platform. However the New features and improvements that have been made to C# are welcome because they are aimed at aiding productivity. Paulo Morgado explains what they are, and how to use them. 

up to 17.9% less memory required for .NET 5 FlexGrid row auto sizing.
rid painting is up to 1.3 times faster for .NET 5 than for .NET Framework 4.5.2.
fit the data in all columns up to 1.7 times faster for .NET 5.
 

.NET 5 and .NET Core SDK version pinning | AppVeyor 

At work, we are planning to migrate our WPF application from .NET Framework 4.7 to .NET Core 3.0. The main reason for doing so is that it was always a big pain to organize the updates of the .NET Framework on our customer machines. So being able to bundle .NET Core with our application is a big plus for us. Then, for sure, we are looking for the performance improvements brought by .NET Core and finally the new capabilities brought by the fast pace of innovation of .NET Core.