Windows 10: .NET Core 1.0 and 1.1 will reach End of Life on June 27, 2019

Brink · Feb 19, 2019

.NET Core 1.0 was released on June 27, 2016 and .NET Core 1.1 was released on November 16, 2016. As an LTS release, .NET Core 1.0 is supported for three years. .NET Core 1.1 fits into the same support timeframe as .NET Core 1.0. .NET Core 1.0 and 1.1 will reach end of life and go out of support on June 27, 2019, three years after the initial .NET Core 1.0 release.

After June 27, 2019, .NET Core patch updates will no longer include updated packages or container images for .NET Core 1.0 and 1.1. You should plan your upgrade from .NET Core 1.x to .NET Core 2.1 or 2.2 now.

Upgrade to .NET Core 2.1

The supported upgrade path for .NET Core 1.x applications is via .NET Core 2.1 or 2.2. Instructions for upgrading can be found in the following documents:

Migrate to .NET Core 2.1

Migrate to ASP.NET Core 2.1

Note: The migration documents are written for .NET Core 2.0 to 2.1 migration, but equally apply to .NET Core 1.x to 2.1 migration.

.NET Core 2.1 is a long-term support (LTS) release. We recommend that you make .NET Core 2.1 your new standard for .NET Core development, particularly for apps that are not updated often.

.NET Core 2.0 has already reached end-of-life, as of October 1, 2018. It is important to migrate applications to at least .NET Core 2.1.

Microsoft Support Policy

Microsoft has a published support policy for .NET Core. It includes policies for two release types: LTS and Current.

.NET Core 1.0, 1.1 and 2.1 are LTS releases. .NET Core 2.0 and 2.2 are Current releases.

LTS releases are designed for long-term support. They included features and components that have been stabilized, requiring few updates over a longer support release lifetime. These releases are a good choice for hosting applications that you do not intend to update.

Current releases include new features that may undergo future change based on feedback. These releases are a good choice for applications in active development, giving you access to the latest features and improvements. You need to upgrade to later .NET Core releases more often to stay in support.

Both types of releases receive critical fixes throughout their lifecycle, for security, reliability, or to add support for new operating system versions. You must stay up to date with the latest patches to qualify for support.

The .NET Core Supported OS Lifecycle Policy defines which Windows, macOS and Linux versions are supported for each .NET Core release.
Click to expand...

Source: .NET Core 1.0 and 1.1 will reach End of Life on June 27, 2019 | .NET Blog

:)

Brink · Feb 19, 2019

.NET Core October 2018 Update now released

Today, we are releasing the .NET Core October 2018 Update. This update includes .NET Core 2.1.5 and .NET Core SDK 2.1.403 and contains important reliability fixes.

Getting the Update

The latest .NET Core updates are available on the .NET Core download page. This update is also included in the Visual Studio 15.8.7 update, which is also releasing today.

See the .NET Core 2.1.5 release notes for details on the release including a detailed commit list.

Docker Images

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

microsoft/dotnet

microsoft/dotnet-samples

Note: Look at the “Tags” view in each repository to see the updated Docker image tags.

Note: You must re-pull base images in order to get updates. The Docker client does not pull updates automatically.

Lifecycle Updates

The end of life schedule for .NET Core 2.0 was updated and announced in June and that day has arrived. .NET Core 2.0 was released August 14, 2017 and really began to open the path to the capabilities envisioned for .NET Core. Instructions for upgrading from .NET Core 2.0 to .NET Core 2.1 can be found in the following documents:

Migrate from .NET Core 2.0 to 2.1

Migrate from ASP.NET Core 2.0 to 2.1

.NET Core 2.1 has been declared the long-term support (LTS) release. We recommend that you make .NET Core 2.1 your new standard for .NET Core development.

Azure App Services

Deployment of .NET Core 2.1.5 to Azure App Services has begun and the West Central US region will be live this morning. Remaining regions will be updated over the next few days.

App Services and end of life .NET Core versions

We are working through a maintenance plan for the versions of .NET Core and the .NET Core SDK which will be available on Azure App Services. Currently the available versions include some which are quite old and need to be removed. The essential idea will be to keep the latest patch version of in-support version channels (eg 1.0, 2.1, etc). Because the SDK is capable of building applications for any version of the runtime, only the latest will be retained.

.NET Core 2.0 reached end of life on October 1, 2018 and is no longer eligible for support or updates which means that it should be removed from App Services. However, we understand that many applications on App Services use 2.0 and removing it from the service too quickly would be disruptive. To give ample opportunity to migrate applications, we are going to ‘attach’ the 2.0 App Services maintenance to the .NET Core 1.0 and 1.1 end of life schedule, which concludes June 27, 2019 per the .NET Core Support Policy. After that date, .NET Core 1.0, 1.1 and 2.0 will be removed from Azure App Services.
Click to expand...

Source: .NET Core October 2018 Update | .NET Blog

Brink · Feb 19, 2019

.NET Core 3 Preview 1 and Open Source Windows Desktop Frameworks

Today, we are announcing .NET Core 3 Preview 1. It is the first public release of .NET Core 3. We have some exciting new features to share and would love your feedback. You can develop .NET Core 3 applications with Visual Studio 2019 Preview 1, Visual Studio for Mac and Visual Studio Code.

Download and get started with .NET Core 3 Preview 1 right now on Windows, Mac and Linux.

You can see complete details of the release in the .NET Core 3 Preview 1 release notes. Please report any issues you find in the comments or at dotnet/core #2099.

Visual Studio 2019 will be the release to support building .NET Core 3 applications and the preview was also released today so we also encourage you to check that out.

.NET Core 3 is a major update which adds support for building Windows desktop applications using Windows Presentation Foundation (WPF), Windows Forms, and Entity Framework 6 (EF6). ASP.NET Core 3 enables client-side development with Razor Components. EF Core 3 will have support for Azure Cosmos DB. It will also include support for C# 8 and .NET Standard 2.1 and much more!

.NET Framework 4.8

Before diving into .NET Core 3 let’s take a quick look at .NET Framework. Next year we will ship .NET Framework 4.8. With monitors supporting 4K and 8K resolutions we are adding better support for high DPI to WPF and Windows Forms. Many .NET applications use browser and media controls, which are based on older versions of Internet Explorer and Windows Media player. We are adding new controls that use the latest browser and media players in Windows 10 and support the latest standards. And WPF and Windows Forms applications will have access to Windows UI XAML Library (WinUI) via XAML Islands for modern look and touch support. Visual Studio 2019 is based on .NET Framework and uses many of these features. For more information on .NET Framework 4.8 see our post: Update on .NET Core 3.0 and .NET Framework 4.8.

Windows Desktop Comes to .NET Core

The first two versions of .NET Core focused primarily on supporting web applications, web APIs, IoT and console applications. .NET Core 3 adds support for building Windows desktop applications using WPF and Windows Forms frameworks and modern controls and Fluent styling from the Windows UI XAML Library (WinUI) via XAML Islands.

Many desktop applications today use Entity Framework for data access and so we are supporting Entity Framework 6 on .NET Core 3 as well. These frameworks enable developers building Windows desktop applications to take advantage of the new features in .NET Core such as side by side deployment, self-contained applications (shipping .NET Core inside the application), the latest improvements in CoreFX, and more.

WPF, Windows Forms, and WinUI Open Sourced

On November 12, 2014 we announced the open sourcing of .NET Core. It has been a tremendous success. The .NET platform has received over 60,000 community accepted pull requests from more than 3700 companies outside of Microsoft.

Today, we are excited to announce that are open sourcing WPF, Windows Forms, and WinUI, so the three major Windows UX technologies will be open sourced. For the first time ever, the community will be able to see the development of WPF, Windows Forms, and WinUI happen in the open and we will take contributions for these frameworks on .NET Core. The first wave of code will be available in GitHub today and more will appear over the next few months.

WPF and Windows Forms projects are under the stewardship of the .NET Foundation which also announced changes today so that the community will directly guide foundation operations. It is also expanding the current sponsors – Red Hat, JetBrains, Google, Unity, Microsoft and Samsung, by also welcoming Pivotal, Progress Telerik and Insight. This new structure will help the .NET Foundation scale to meet the needs of the growing .NET open source ecosystem.

Truly an exciting time to be a .NET developer!
Click to expand...

Read more: Announcing .NET Core 3 Preview 1 and Open Sourcing Windows Desktop Frameworks | .NET Blog

See also: Announcing Open Source of WPF, Windows Forms, and WinUI - Windows 10 Forums

Tweet

— Twitter API (@User) View on Twiiter

Brink · Feb 19, 2019

.NET Core October 2018 Update - NET Core 1.0 and 1.1

Today, we are releasing the .NET Core October 2018 Update for 1.0 and 1.1. This update includes .NET Core 1.0.13, 1.1.10 and .NET Core SDK 1.1.11.

Security

CVE-2018-8292: .NET Core Information Disclosure Vulnerability

Microsoft is aware of a security feature bypass vulnerability that exists when .NET Core when HTTP authentication information is inadvertently exposed in an outbound request that encounters an HTTP redirect. An attacker who successfully exploited this vulnerability could use the information to further compromise the web application.

The update addresses the vulnerability by correcting how .NET Core applications handles HTTP redirects.

Getting the Update

The latest .NET Core updates are available on the .NET Core download page.

Today’s releases are listed as follows:

.NET Core 1.1.10

.NET Core 1.0.13

Docker Images

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

microsoft/dotnet

Note: Look at the “Tags” view in each repository to see the updated Docker image tags.

Note: You must re-pull base images in order to get updates. The Docker client does not pull updates automatically.

Azure App Services deployment

Deployment to Azure App Services has begun and the West Central US region will be live this morning. Remaining regions will be updated over the next few days and deployment is expected to be complete by end of week.
Click to expand...

Source: .NET Core October 2018 Update - NET Core 1.0 and 1.1 | .NET Blog

Windows 10: .NET Core 1.0 and 1.1 will reach End of Life on June 27, 2019

.NET Core 1.0 and 1.1 will reach End of Life on June 27, 2019

.NET Core 1.0 and 1.1 will reach End of Life on June 27, 2019

.NET Core 1.0 and 1.1 will reach End of Life on June 27, 2019

.NET Core 1.0 and 1.1 will reach End of Life on June 27, 2019 - Similar Threads - NET Core reach

1 user 1 computer Word 2019

1 user 1 computer Word 2019

1 user 1 computer Word 2019

New Firefox coming June 1

Announcing .NET Core 3.1 Preview 1

Announcing .NET Core 3.0 Release Candidate 1

Intel at COMPUTEX 2019 on May 28 to June 1

Core #1 #2 working 100%

Running on 1 core out of 4

Users found this page by searching for:

.net core 1 end