Upgrade from `netcoreapp3.0` to LTS (or STS) version
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system
Research direction
Start by reading non-lts/MultipleTargets.csproj and non-lts/ThisShouldNeverBeFlagged.csproj at the linked target-framework lines. Check how each project is intended to handle the unsupported netcoreapp3.0 target, then verify that both projects target a supported LTS or STS version, or are explicitly covered by dotnet-versionsweeper.json if the target is intentional.
Written by the indexing model from the issue text.
Description
The following project file(s) target a .NET version that's no longer supported.
This is an auto-generated issue, detailed and discussed in dotnet/docs#22271.
| Target version | End of life | Release notes | Nearest LTS TFM version |
|---|---|---|---|
netcoreapp3.0 |
March, 03 2020 | netcoreapp3.0 release notes | net8.0 |
Consider upgrading projects to either the Standard Term Support (STS) or Long Term Support (LTS) versions.
If any of these projects listed in this issue are intentionally targeting an unsupported version,
you can optionally configure to ignore these results in future automation executions.
Create a (or update the) dotnet-versionsweeper.json file at the root of the repository and
add an ignore entry following the
globbing patterns detailed here.
{
"ignore": [
"**/path/to/example.csproj"
]
}
- Dominant language
- C#
- Stars
- 65
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/versionsweeper
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/versionsweeper#145 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
dotnet/versionsweeper#108 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
dotnet/versionsweeper#103 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
dotnet/versionsweeper#101 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
dotnet/versionsweeper#99 ·
All issues in dotnet/versionsweeper
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·