Here’s a look at a handful of the changes since our last alpha:

• Overhauled spacing utilities to use a numerical tiering (to avoid confusion with grid tiers).
• Continued refactoring efforts to replace markup-specific selectors with classes across several components (including pagination, lists, and more). Still more to do here with additional components.
• Reverted media queries and grid containers from rems to pixels as viewports are not affected by font-size. See #17403 for details. We’ve got a ton of grid work left, too. Feel free to follow along with#18471.
• Reverted .0625rem width borders to 1px for more consistent component borders that avoid zoom and font-size bugs across browsers.
• Renamed .img-responsive to .img-fluid to avoid future confusion on the various responsive image solutions out there.
• Replaced ZeroClipboard with clipboard.js for Flash-independent copy buttons.
• Inputs and buttons now share the same border variable to ensure components are always sized similarly.
• Updated all pseudo-element selectors to use the spec’s preferred double colon (e.g., ::before as opposed to :before).
• Cards now have outline variants and mixins to support extending base classes further.
• Utility classes for floats and text alignment now have responsive ranges. This means we’ve dropped the non-responsive classes to avoid duplication.
• Added support for jQuery 2.
• And hundreds more Sass improvements, bug fixes, documentation updates, and more. 

This bug-fix update resolves the following issues:

ReSharper Build couldn’t build a project if MSBuild was installed as part of Visual Studio 2019 Preview 1 (RSRP-472694).
Visual Studio froze on JavaScript debugging (RSRP-472802).
Inconsistent default state around ‘Inconsistent Naming‘ inspection (RSRP-472812).
A false positive for NUnit TestCase (RSRP-472787).
Unit test coverage highlighting is not shown for projects targeting .NET Framework 3.5 and lower (DCVR-9525).
False “Cannot convert type” error for Promise in TypeScript.
Find Usages did not process bodies of #define macros when looking for textual occurrences (RSCPP-24977).
“Remove unused parameter” quick-fix was broken in C++ (RSCPP-25094).
 

The new SameSite behavior has been the default in Firefox Nightly since Nightly 75 (February 2020). At Mozilla, we’ve been able to explore the implications of this change. Starting with Firefox 79 (June 2020), we rolled it out to 50% of the Firefox Beta user base. We want to monitor the scope of any potential breakage. 

We created this collaborative space for sharing checklists that help ensure software quality, guide you through crisis and other helpful stuff for devs 

• We have two new refactorings for global usings, Extract Global Using and Inline Global Using, with Find Usages support for this feature.
• For nullable reference types, we’ve split the “should never be null” warning into two categories: one for those who look at NRT annotation and one for those who have a runtime check for null. We’ve also added a setting to enable runtime enforced not null warnings only, and supported [MemberNotNull] and [MemberNotNullWhen] annotations.
• We’ve implemented generic attributes support for C#11. 

Here is a partial list of the C# coding standards my team uses and advocates. Most of these are industry-wide conventions and thus using them will ensure that your code is easily readable by people who are not you.  

Now you can upgrade any .NET application to the latest version of .NET inside of Visual Studio! We are happy to introduce it as a Visual Studio extension and will upgrade your .NET Framework or .NET Core web- and desktop apps. In this video, Olia shows you how to get the extension and start to update your projects to the latest version of NET in minutes.