With the latest release of ASP.NET Core, developers are wondering what the next step is for their web apps and how to convert it over to the new ASP.NET Core.

The .NET Micro Framework team is pleased to announce the release of .NET Micro Framework 4.4. We fixed several long outstanding issues as well as improved the reliability of lwIP network stack and debugging experience through Visual Studio 2015.

• WMI Provider MSI still failing to install in 16.6
• View History on context menu in Solution Explorer doesn't do anything
• Cannot generate shim for X509Certificate2 with Visual Studio 2019 16.6.0
• Add Controller and Add New Scaffolded Item dialogs are not showing all data contexts after upgrading Visual Studio Enterprise 16.5.6->16.6.0
• Cannot open new json file
• About Microsoft Visual Studio frozen.
• Visual Studio 2019 16.6.0 Microsoft Fakes Issue
• VSSDK IVsHierarchy Regression in VS 16.6.x
• Windows 10 SDK (10.0.19041.1)- ARM64 memcpy crashes when accessing unaligned uncached memory
• Add script to SQL Server Database project does not open User Scripts list
• Fakes generation with ref argument
• Frequent soft hang with Code Analysis callstack in Open Folder project
• Visual Studio Class Designer dark theme support
• Added support for Text Template Transformation Toolkit (T4) in .NET Core projects
• Separate IntelliCode team completions model acquisition from model production.
• Addressed an issue where users may have experienced critical update or installation failures due to the WMIProvider package that would block use of the IDE. Failures in this component no longer block use of the IDE.
• Fixed a problem causing the product to stop responding when working with Xamarin projects on certain scenarios.
• Fixed a bug where VS would crash when attempting to decrypt an invalid UWP code-signing certificate

If you're migrating an app to .NET 6, the breaking changes listed here might affect you. Changes are grouped by technology area, such as ASP.NET Core or Windows Forms. 

Today we announce .NET 7 Release Candidate 1. This is the first of two release candidates (RC) for .NET 7 that are supported in production. 

.NET 7 brings your apps increased performance and new features for C# 11/F# 7, .NET MAUI, ASP.NET Core/Blazor, Web APIs, WinForms, WPF and more. With .NET 7, you can also easily containerize your .NET 7 projects, set up CI/CD workflows in GitHub actions, and achieve cloud-native observability.

Thanks to the open-source .NET community for your numerous contributions that helped shape this .NET 7 release. 28k contributions made by over 8900 contributors throughout the .NET 7 release!

.NET remains one of the fastest, most loved, and trusted platforms with an expansive .NET package ecosystem that includes over 330,000 packages. 

Asynchronous Main (it is going to be released in version 7.1)
Default Literal (it is going to be released in version 7.1)
Readonly ref (it is going to be released in version 7.2)
Default interface methods (it is going to be released in version 8.0)
Optional tuple names (to be released in 7.1)
 

TL;DR: .NET 7 is fast. Really fast. A thousand performance-impacting PRs went into runtime and core libraries this release, never mind all the improvements in ASP.NET Core and Windows Forms and Entity Framework and beyond. It’s the fastest .NET ever. If your manager asks you why your project should upgrade to .NET 7, you can say “in addition to all the new functionality in the release, .NET 7 is super fast.” 

• DateTime.Now = Cannot provide the value: host value not found
• MSVC codegen error vector reverse_iterator x64 C++17 debug build
• C2440 error building atlenc.h with /permissive- in VS 16.4 Preview 1
• Last Visual Studio update broke NTLM authentication on Android (seems like new version of Momo would be a reason)
• Visual Studio 16.3.1 fails at compiling template code (e.g. from Basler Pylon SDK)
• Using TypeScript 3.7 for IntelliSense
• XCode 11.3 is too new all of a sudden after update to 8.4
• You uploaded an APK or Android App Bundle with invalid or missing signing information for some of its files. You need to create a valid signed APK or Android App Bundle.
• Unable to Run UWP project
• JavaScript IntelliSense not working after update 16.4.1
• Xib : Xcode is to new(rendering problem when using custom components)
• Storyboard error: 'Xcode is too new'
• Stability improvements for debugging watchOS applications.
• Adds Xcode 11.3 SDK support.
• Fixed crash when fstack-protector-strong flag is enabled.
• Fixed some inconsistent behavior with Debugger.

Security Advisory Notice

CVE-2020-0602 ASP.NET Core Denial of Service Vulnerability
CVE-2020-0603 ASP.NET Core Remote Code Execution Vulnerability
CVE-2020-0605 .NET Core Remote Code Execution Vulnerability
CVE-2020-0606 .NET Core Remote Code Execution Vulnerability