We are excited to release .NET 6 Release Candidate 2. It is the second of two “go live” release candidate releases that are supported in production. For the last couple months, the team has been focused exclusively on quality improvements. There are a lot of new features in the release, which only fully come together near the end. The team is currently validating end-to-end workflows to find the places where design intentions and technical reality don’t yet fully match. That’s led to teams tightening leaky pipes and paving paths all the way to their destination. 

We’re excited to announce the release of .NET Core 3.0. It includes many improvements, including adding Windows Forms and WPF, adding new JSON APIs, support for ARM64 and improving performance across the board. C# 8 is also part of this release, which includes nullable, async streams, and more patterns. F# 4.7 is included, and focused on relaxing syntax and targeting .NET Standard 2.0. You can start updating existing projects to target .NET Core 3.0 today. The release is compatible with previous versions, making updating easy. 

• Delete option is missing from solution explorer context menu in Xamarin Forms Android projects.
• Xamarin.Android: Can't select target framework 28 in Android Manifest settings.
• Could not load file or assembly 'Microsoft.VisualStudio.Web.PageInspector.Loader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
• "There was an error running the selected code generator" when trying to create a new view.
• Android Berechtigungsliste ist leer-Android permission list is empty.
• Missing icons for .axml files in Visual Studio 2019.
• axml icons are not displayed.
• Visual Studio extensions may fail to install attempting to overwrite core NuGet files.
• C# switch statement on a constant expression may produce bad compiler errors. 

• Solution Explorer: touch pad gesture scroll is too sensitive.
• C++/CLI: std::move causes std::unique_ptr parameter to be destructed before function call.
• live share shows "failed to sign in" .
• VS symbol search fails to find symbols.
• Undo randomly stops working.
• VS "Go to defintion" functionality frequently does not work.
• Linux CMake Intellisense HeaderCache not downloading headers for 15.8.0 Preview 4.0.
• When opening a project that requires elevated permissions, Visual Studio does not automatically open the selected project after restarting elevated.
• vcpkgsrv.exe crashes.
• New Visual Studio Code keymap not applying?. 

• 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. 

Download SQL Server 2017 for Windows  

Microsoft® SQL Server® 2017 Feature Pack  

Microsoft SQL Server 2017 Developer Edition:
https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B/SQLServer2017-x64-ENU-Dev.iso

Microsoft SQL Server 2017 Evaluation:
https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B/SQLServer2017-x64-ENU.iso


Microsoft SQL Server 2017 Express:
https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B/SQLEXPRADV_x64_ENU.exe
https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B/SQLEXPR_x64_ENU.exe
https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B/SqlLocalDB.msi

https://download.microsoft.com/download/E/F/2/EF23C21D-7860-4F05-88CE-39AA114B014B/SQLRules_x64_ENU.exe

• To import various symbols please adjust the paths in the following way:
  
• angular2/core -> @angular/core
  
• angular2/compiler -> @angular/compiler
  
• angular2/common -> @angular/common
  
• angular2/platform/browser -> @angular/platform-browser (applications with precompiled templates) + @angular/platform-browser-dynamic (applications that compile templates on the fly)
  
• angular2/platform/server -> @angular/platform-server
  
• angular2/testing -> @angular/core/testing (it/describe/..) + @angular/compiler/testing (TestComponentBuilder) + @angular/platform-browser/testing
  
• angular2/upgrade -> @angular/upgrade
  
• angular2/http -> @angular/http
  
• angular2/router -> @angular/router-deprecated (snapshot of the component router from beta.17 for backwards compatibility)
  
• new package: @angular/router - component router with several breaking changes  
  

Fixed In This Release of Visual Studio 2019 version 16.5

• Team Explorer not loading after update to mandatory latest visual studio version for Visual studio 2019
• Find Highlighting Fails when Matching with Match Case Disabled and Regex Option Enabled

Security Advisory Notice

CVE-2020-1108 .NET Core Denial of Service Vulnerability

A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET Core application. The security update addresses the vulnerability by correcting how the .NET Core web application handles web requests.

CVE-2020-1161 .NET Core Denial of Service Vulnerability

A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application. The security update addresses the vulnerability by correcting how the ASP.NET Core web application handles web requests. 

Security Advisory Notices

CVE-2019-1077 Visual Studio Extension Auto Update Vulnerability

An elevation of privilege vulnerability exists when the Visual Studio Extension auto-update process improperly performs certain file operations. An attacker who successfully exploited this vulnerability could delete files in arbitrary locations. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by securing locations the Visual Studio Extension auto-update performs file operations in.

CVE-2019-1075 ASP.NET Core Spoofing Vulnerability

A spoofing vulnerability exists in ASP.NET Core that could lead to an open redirect. An attacker who successfully exploited the vulnerability could redirect a targeted user to a malicious website. To exploit the vulnerability, an attacker could send a link that has a specially crafted URL and convince the user to click the link.

The security update addresses the vulnerability by correcting how ASP.NET Core parses URLs. Details can be found in the .NET Core release notes.

CVE-2019-1113 WorkflowDesigner XOML deserialization allows code execution

A XOML file referencing certain types could cause random code to be executed when the XOML file is opened in Visual Studio. There is now a restriction on what types are allowed to be used in XOML files. If a XOML file containing one of the newly unauthorized types is opened, a message is displayed explaining that the type is unauthorized.

For further information, please refer to https://support.microsoft.com/en-us/help/4512190/remote-code-execution-vulnerability-if-types-are-specified-in-xoml.

background-clip is one of those properties I've known about for years, but rarely used. Maybe just a couple of times as part of a solution to a Stack Overflow question. Until last year, when I started creating my huge collection of sliders. Some of the designs I chose to reproduce were a bit more complex and I only had one element available per slider, which happened to be an input element, meaning that I couldn't even use pseudo-elements on it. Even though that does work in certain browsers, the fact that it works is actually a bug and I didn't want to rely on that. All this meant I ended up using backgrounds, borders, and shadows a lot. I also learned a lot from doing that and this article shares some of those lessons.