What’s in this build? Significant performance improvements were made, shared projects are now supported, code inspection severity can be configured, settings for our unit test runner can be edited, various updates to the NuGet tool window UI, and more. Check out the list of fixes in this build if you feel like digging into details. 

• TLS 1.0: The request was aborted: Could not create SSL/TLS secure channel.
• Task List with filter set to Entire Solution doesnt display tasks/todos when the file is closed.
• Fatal error C1001: An internal error has occurred in the compiler.
• VS 2019 Preview 1 - EF6 edmx file cannot be saved.
• vcruntime140.dll should be made available on Microsoft Symbol Server.
• Static Analyser, Custom Rule Set (C++) does not execute included default sets.
• VS2019 Preview: Azure Function publishing does not work.
• References window does not remember its position.
• Missing formatting option for pointers and references.
• Microsoft.TeamFoundation.Client, Version=15.0.0.0 assembly not found when create a new web project. 

Not because there aren’t people who actually enjoy working in an open office, there are. Quite a few, actually. But they’re in the distinct minority. The vast majority of people either dislike the open office or downright hate it. So how is that going to work, exactly? 

How to install and set up Visual Studio 2019 for .NET Development 

.NET 5 Preview 7 is now available and is ready for evaluation. Here’s what’s new in this release:

• Blazor WebAssembly apps now target .NET 5
• Updated debugging requirements for Blazor WebAssembly
• Blazor accessibility improvements
• Blazor performance improvements
• Certificate authentication performance improvements
• Sending HTTP/2 PING frames
• Support for additional endpoints types in the Kestrel sockets transport
• Custom header decoding in Kestrel
• Other minor improvements 

• Updated the version of .NET that the debugger uses for running its own C# code to .NET 5 

ASP.NET Core and Blazor futures Q&A | DIS201H

#MSBuild

Join us for a discussion on the future of web development with the ASP.NET Core team. Get the team's perspective first-hand on the roadmap for ASP.NET Core and Blazor in .NET 8 and get all of your burning questions answered. We discuss Blazor, Native AOT, cloud native development, and anything else that you want to ask us about. 

Elemental.JsonResource

Json Resource file support in C# projects.

This provides an alternative to using resx files to defined resources in C# projects. The benefits over resx are:

• human readable file format (try writing resx xml from scratch without documentation)
• generated C# code doesn't get included in project/source control
• Doesn't require modifying the .csproj (adding a single resx file will add ~12 lines to your csproj file)
• Doesn't require Visual Studio to function. (resx files don't work in VS Code for example) 

Why could there not be another tool that allowed a development team to harness their existing source control systems, but make database changes a part of the workflow? Enter SQL Source Control by Redgate. 

Announcing New ASP.NET Core and Web Development Features in Visual Studio 2017