Windows 10: .NET Core January 2020 Updates - 2.1.15, 3.0.2, and 3.1.1

Brink · Jan 17, 2020

Today, we are releasing the .NET Core January 2020 Update. These updates also contain security and reliability fixes. See the individual release notes for details on updated packages.

NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version. Information needed to make this choice will be seen on the download page. If you use other development environments, we recommend using the latest SDK release.

.NET Core 3.1.1 and .NET Core SDK ( Download | Release Notes )

.NET Core 3.0.2 and .NET Core SDK ( Download | Release Notes )

.NET Core 2.1.15 and .NET Core SDK ( Download | Release Notes )

Getting the Update

The latest .NET Core updates are available on the .NET Core download page. This update will be included in a future update of Visual Studio.

See the .NET Core release notes ( 2.1.15 | 3.0.2 | 3.1.1 ) for details on the release, including issues fixed and affected packages.

Docker Images

.NET Docker images have been updated for today’s release. The following repos have been updated.

dotnet/core/sdk: .NET Core SDK

dotnet/core/aspnet: ASP.NET Core Runtime

dotnet/core/runtime: .NET Core Runtime

dotnet/core/runtime-deps: .NET Core Runtime Dependencies

dotnet/core/samples: .NET Core Samples

Note: You must pull updated .NET Core container images to get this update, with either docker pull or docker build –pull.

Security

CVE-2020-0602: ASP.NET Core Denial of Service Vulnerability
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. Microsoft is aware of a denial of service vulnerability exists when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application. The update addresses the vulnerability by correcting how the ASP.NET Core web application handles web requests.

CVE-2020-0603: ASP.NET Core Remote Code Execution Vulnerability
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. Microsoft is aware of a remote code execution vulnerability exists in ASP.NET Core software when the software fails to handle objects in memory. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application. The update addresses the vulnerability by correcting how the ASP.NET Core web application handles in memory.

CVE-2020-0605: .NET Core Remote Code Execution Vulnerability
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. Microsoft is aware of a remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of .NET Core. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. The security update addresses the vulnerability by correcting how .NET Core checks the source markup of a file.

CVE-2020-0606: .NET Core Remote Code Execution Vulnerability
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. Microsoft is aware of a remote code execution vulnerability exists in .NET software when the software fails to check the source markup of a file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of .NET Core. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. The security update addresses the vulnerability by correcting how .NET Core checks the source markup of a file.

Rahul Bhandari
Click to expand...

Source: https://devblogs.microsoft.com/dotne...-january-2020/

:)

Brink · Jan 17, 2020

Announcing .NET Core 3 Preview 2

.NET Core 3.0 Preview 2 is now available and it includes a bunch of new updates to ASP.NET Core.

Here's the list of what's new in this preview:

Razor Components

SignalR client-to-server streaming

Pipes on HttpContext

Generic host in templates

Endpoint routing updates

Get started

To get started with ASP.NET Core in .NET Core 3.0 Preview 2 install the .NET Core 3.0 Preview 2 SDK

If you're on Windows using Visual Studio, you'll also want to install the latest preview of Visual Studio 2019.

Upgrade an existing project

To upgrade an existing an ASP.NET Core app to .NET Core 3.0 Preview 2, follow the migrations steps in the ASP.NET Core docs.

Add package for Json.NET

As part of the work to tidy up the ASP.NET Core shared framework, Json.NET is being removed from the shared framework and now needs to be added as a package.

To add back Json.NET support to an ASP.NET Core 3.0 project:

Add a package reference to Microsoft.AspNetCore.Mvc.NewtonsoftJson

Update your ConfigureServices method to include a call to AddNewtonsoftJson().

services.AddMvc()
.AddNewtonsoftJson();

Runtime compilation removed

As a consequence of cleaning up the ASP.NET Core shared framework to not depend on Roslyn, support for runtime compilation of pages and views has also been removed in this preview release. Instead compilation of pages and views is performed at build time. In a future preview update we will provide a NuGet packages for optionally enabling runtime compilation support in an app.

Other breaking changes and announcements

For a full list of other breaking changes and announcements for this release please see the ASP.NET Core Announcements repo...
Click to expand...

Read more:

Announcing .NET Core 3 Preview 2 | .NET Blog

ASP.NET Core updates in .NET Core 3.0 Preview 2 | ASP.NET Blog

Tweet

— Twitter API (@user) View on Twiiter[/quote]

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Brink · Jan 17, 2020

Announcing .NET Core 3.1 Preview 1

Today, we’re announcing .NET Core 3.1 Preview 1. .NET Core 3.1 will be a small release focused on key improvements in Blazor and Windows desktop, the two big additions in .NET Core 3.0. It will be a long term support (LTS) release with an expected final ship date of December 2019.

You can download .NET Core 3.1 Preview 1 on Windows, macOS, and Linux.

.NET Core 3.0 SDK and Runtime

Docker images

ASP.NET Core and EF Core are also releasing updates today.

Visual Studio 16.4 Preview 2 and is also releasing today. It is a recommended update to use .NET Core 3.1 Preview 1. Visual Studio 16.4 includes .NET Core 3.1, so just updating Visual Studio will give you both releases.
Details:

.NET Core 3.1 release notes

Known Issue: The Visual Studio 16.4 installer may uninstall the .NET Core 3.0 Runtime when it installs .NET Core 3.1. We recommend you re-in-install or repair the .NET Core 3.0 SDK in that case.

Improvements

There are several targeted improvements planned for .NET Core 3.1. The following improvements are not available yet, but are expected in later previews.

In .NET Core 3.0, the .NET Core Desktop Runtime Installer (includes WPF and Windows Forms) does not install the .NET Core Runtime (includes CoreFX and CoreCLR) for you. We will be changing that, so that the Desktop Runtime installer is self-sufficient. The Runtime and Hosting Bundle, for server scenarios, already works this way.

C++/CLI was a promised component of the .NET Core 3.0 release. It was delivered, given that it is a required dependency of WPF, but a developer experience in Visual Studio and the SDK was missing. We will be delivering that experience with .NET Core 3.1 and Visual Studio 16.4. C++/CLI is only supported on Windows.

macOS 10.15 Catalina includes a new security requirement, that applications must be notarized. We will be satisfying these requirements for the .NET Core SDK, for .NET Core 3.1 and all other supported .NET Core releases. If you are using .NET Core to deliver macOS applications, we would appreciate working with you on notarization requirements.

Closing

The primary goal of .NET Core 3.1 is to polish the features and scenarios we delivered in .NET Core 3.0. .NET Core 3.1 will be a long term support (LTS) release, supported for at least 3 years.

Please install and test .NET Core 3.1 Preview 1 and give us feedback. It is not yet supported or recommended for use in production.

If you missed it, check out the .NET Core 3.0 announcement from last month.

Richard Lander
Program Manager, .NET Team
Click to expand...

Source: https://devblogs.microsoft.com/dotne...3-1-preview-1/

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Brink · Jan 17, 2020

Announcing .NET Core 3 Preview 2

.NET Core 3.0 Preview 2 is now available and it includes a bunch of new updates to ASP.NET Core.

Here's the list of what's new in this preview:

Razor Components

SignalR client-to-server streaming

Pipes on HttpContext

Generic host in templates

Endpoint routing updates

Get started

To get started with ASP.NET Core in .NET Core 3.0 Preview 2 install the .NET Core 3.0 Preview 2 SDK

If you're on Windows using Visual Studio, you'll also want to install the latest preview of Visual Studio 2019.

Upgrade an existing project

To upgrade an existing an ASP.NET Core app to .NET Core 3.0 Preview 2, follow the migrations steps in the ASP.NET Core docs.

Add package for Json.NET

As part of the work to tidy up the ASP.NET Core shared framework, Json.NET is being removed from the shared framework and now needs to be added as a package.

To add back Json.NET support to an ASP.NET Core 3.0 project:

Add a package reference to Microsoft.AspNetCore.Mvc.NewtonsoftJson

Update your ConfigureServices method to include a call to AddNewtonsoftJson().

services.AddMvc()
.AddNewtonsoftJson();

Runtime compilation removed

As a consequence of cleaning up the ASP.NET Core shared framework to not depend on Roslyn, support for runtime compilation of pages and views has also been removed in this preview release. Instead compilation of pages and views is performed at build time. In a future preview update we will provide a NuGet packages for optionally enabling runtime compilation support in an app.

Other breaking changes and announcements

For a full list of other breaking changes and announcements for this release please see the ASP.NET Core Announcements repo...
Click to expand...

Read more:

Announcing .NET Core 3 Preview 2 | .NET Blog

ASP.NET Core updates in .NET Core 3.0 Preview 2 | ASP.NET Blog

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Windows 10: .NET Core January 2020 Updates - 2.1.15, 3.0.2, and 3.1.1

.NET Core January 2020 Updates - 2.1.15, 3.0.2, and 3.1.1

.NET Core January 2020 Updates - 2.1.15, 3.0.2, and 3.1.1

.NET Core January 2020 Updates - 2.1.15, 3.0.2, and 3.1.1

.NET Core January 2020 Updates - 2.1.15, 3.0.2, and 3.1.1 - Similar Threads - NET Core January

Fix Fortnite Matchmaking Error 1, 2 or 3

Stopcodes 1. UNEXPECTED_STORE_EXCEPTION 2.REGISTRY_FILTER_DRIVER_EXCEPTION 3.MEMORY MANAGEMENT

multiple monitors change 1/2 to 1 and 2

Windows 10 update 3/1/2020

VPN error 2/1/2020

Critical Update 1/15/2020?

Announcing .NET Core 3 Preview 2

Core #1 #2 working 100%

DIMM slot 1, 3 or DIMM slot 2, 4?

Users found this page by searching for:

win 10 build with cve 2020-0603

Security Update for .NET Core (January 2020)