Skip to content

Dependency drift across .NET 8 and .NET 9 packages #8361

Description

@baronfel

Product

dotnet CLI (dotnet new)

Describe The Bug

Chatted with @sayedihashimi and @phenning today about if/when VS should update to 9.x Template Engine packages, and we saw some discrepancies that are concerning.

.NET 8 package:
image

.NET 9 package:
image

The big problems I see are:

  • the .net framework TFM has floated to something VS can't use - net481. VS requires net472 currently. This comes from the Arcade NetFrameworkCurrent property I think?
  • the NS2.0 dependencies dropped the System. deps, which may require work from Phil to consume (he mentioned missing deps in the past)

Were these on purpose? Do we need to have tests to pin the expectations of the VS host so we don't unwittingly violate them?

To Reproduce

N/A

dotnet Info

N/A

Visual Studio Version

No response

Additional context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: infraThe issue is related to engineering infrastructure.triage:transfer-to-sdkIssue should be transferred to dotnet/sdk

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions