Avoid hardcoded NetCoreAppToolCurrent* properties

Open
#109,329 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
build-system

Research direction

Start by reading the repository's Directory.Build.props and global.json, then review how NETCoreAppMaximumVersion becomes available during SDK evaluation. Compare the current NetCoreAppToolCurrent* properties with SDK issue 29949 and define a build that works with newer SDKs and the VMR without requiring a hardcoded shared-framework TFM.

Written by the indexing model from the issue text.

Description

area-Infrastructure

The NetCoreAppToolCurrentVersion is hardcoded to 9.0 which causes issues when building with a newer SDK that doesn't have a shared framework for that given TFM (i.e. inside the VMR). As we already enforce a minimum required SDK version in global.json, it would be better to automatically calculate the NetCoreAppToolCurrentVersion value based on the SDK being used.

The SDK exposes the NETCoreAppMaximumVersion property but unfortunately a little bit too late, after the repo's Directory.Build.props file is imported.

We could avoid the NetCoreAppToolCurrent* properties altogether when the SDK implements https://github.com/dotnet/sdk/issues/29949. That would the ideal path forward.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

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/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.