Rules for dotnet: Replaced target framework property
Open
good first issue
kind/feature
priority/backlog
triage/accepted
- Dominant language
- Java
- Stars
- 6
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
https://learn.microsoft.com/en-us/visualstudio/ide/visual-studio-multi-targeting-overview?view=vs-2022
When moving from .NET framework to modern versions of .NET, the property for targeting the chosen framework in .csproj file has changed.
For example when updating a legacy .NET v4.8 application to .NET 9, what used to be
`v4.8`
would become
` net9.0`
Contributor guide
Research direction
Start with the linked Visual Studio multi-targeting overview and inspect the repository's existing rules for .csproj target framework properties. The change is done when the rules recognize the move from TargetFrameworkVersion, such as v4.8, to TargetFramework, such as net9.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100