question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider upgrading netcoreapp2.0 to 2.1 or 3.1

See original GitHub issue

Currently some projects (Avalonia, Avalonia.Designer.HostApp, Avalonia.DesktopRuntime and NativeEmbedSample) are targeting netcoreapp2.0 (which is EOL since October 1, 2018). So it would make sense to upgrade to a more recent version, preferably LTS. I believe these are the best options:

  • netcoreapp2.1 (LTS, EOL: August 21, 2021)
  • netcoreapp3.1 (LTS, EOL: December 3, 2022)

For more info, .NET Core support policy: https://dotnet.microsoft.com/platform/support/policy/dotnet-core.

If you agree with this change I can make a PR.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:4
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
maxkatz6commented, May 25, 2022

We target netstandard2.0 and net6 where it’s possible now. Avalonia.Designer.HostApp is a special case as explained above.

1reaction
kekekekscommented, Jan 16, 2021
Read more comments on GitHub >

github_iconTop Results From Across the Web

How To Upgrade ASP.NET Core 2.1 To ASP.NET Core 3.1 ...
The very first step for migration is changing the target framework. For this: right-click on Project-> properties and then in project properties ...
Read more >
Migrate from ASP.NET Core 2.0 to 2.1
AspNetCore.App to 2.1.0 which caused conflicts with Entity Framework Core 2.1.1. The recommended solution is to upgrade the .NET Core SDK to 2.1...
Read more >
Why Upgrade Your .NET Core API from 2.x to 3.1?
NET Core 2.1 Web Application, there are no obvious reasons to push that you upgrade immediately. Take a breath of fresh air and...
Read more >
After migrating from .NET Core 2.1 to .NET Core 3.1, ...
Try this first! For anyone suddenly running into this error for seemingly no reason, the error message may be a red herring.
Read more >
Migration from Asp.Net Core 2.2 to 3.1 — Real project
There are many factors that should be considered before migrating a system: costs, effort, ... I upgraded the packages to the 3.1 version....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found