Last Friday, ASP.NET Core quietly switched from supporting .NET Standard 1.* and .NET 4.* to only supporting .NET Core 2.0. This means that ASP.NET Core 1.0/1.1 applications running Mono or the full .NET Framework will not be upgradable to ASP.NET Core 2.0 when it is released in 2-3 months. 

Improved the MSBuild selection logic. The standalone instance inside OmniSharp is now preferred over VS2017, with VS2019 given the highest priority. This ensures that .NET Core 3.0 works correctly. It is also possible manually provide an MSBuild path using OmniSharp configuration, which is then always selected. (omnisharp-roslyn#1541, PR: omnisharp-roslyn#1545)

    {
        "MSBuild": {
            "MSBuildOverride": {
                "MSBuildPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\MSBuild\\15.0\\Bin",
                "Name": "vs2017 msbuild"
            }
        }
    }

4 Things I Like in The New Visual Studio 2022 17.7 Update 

I have a better understanding of the new runtime, the tooling, and the dependencies required to build applications 

I am happy to announce a new series of blog posts dedicated to Specflow. In the first article, I am going to introduce to you the Specflow framework. You will be able to write and execute business-readable specification after 10 minutes. Keep reading! 

This release contains the following improvements and enhancements:

• This release now installs Java™ Development Kit 8, Update 181 (JDK version 8u181). 

These are the customer-reported issues addressed in 15.7.6:

• Visual C++ Redistributable 2017 does not report the install state in a specific registry location.
• In 15.7 users may see extensions load without all of their assets and cause VS to crash. This has been addressed for 15.7.6.
• Visual Studio 2017 version 15.7.5 crashes when opening a solution. 

The State Of Web Workers In 2021  

In the Jungle of .NET Obfuscator Tools 

The cost of JavaScript in 2019