Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Upgrade from `net8.0` to LTS (or STS) version

Open Beginner friendly
  • Is something wrong?
#13,128 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Domain
build-system, documentation

Research direction

Start with the eleven linked .vbproj files and inspect the target framework entry at the referenced lines. Choose a supported LTS or STS target as directed by the issue, update each listed project, and confirm every checklist item is addressed; if a project is intentionally unsupported, follow the documented ignore configuration instead.

Written by the indexing model from the issue text.

Description

dotnet-target-version untriaged

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
net8.0 November, 10 2026 net8.0 release notes net9.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
954
Forks
1.7k
Avg merge
1d 11h
Merged PRs (30d)
64

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/dotnet-api-docs

All issues in dotnet/dotnet-api-docs

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.