Skip to content

Aspire.Hosting.Yarp dependency versions #15909

@paulomorgado

Description

@paulomorgado

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

Aspire.Hosting.Yarp targets net8.0 only.

However, starting with version 13.2.0 it has 10.0.x and 8.0.x dependencies.

This renders it almost impossible to use in solutions with Central Package Management (CPM) with transitive pinning enabled and overriding package versions disabled.

Expected Behavior

An app host targeting net8.0 won't depend on 10.0.x or 9.0.x .NET libraries.

Steps To Reproduce

Create a aspire-starter project targeting net8.0 with CPM with transitive pinning enabled and overriding package versions disabled and add Aspire.Hosting.Yarp.

Exceptions (if any)

No response

.NET Version info

.NET SDK:
 Version:           10.0.201
 Commit:            4d3023de60
 Workload version:  10.0.200-manifests.34a88a22
 MSBuild version:   18.3.0-release-26153-122+4d3023de6

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.26100
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\10.0.201\

.NET workloads installed:
 [wasm-tools-net8]
   Installation Source: VS 18.5.11626.173
   Manifest Version:    10.0.105/10.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.workload.mono.toolchain.net8\10.0.105\WorkloadManifest.json
   Install Type:              Msi

 [maui-windows]
   Installation Source: VS 18.5.11626.173
   Manifest Version:    10.0.20/10.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.maui\10.0.20\WorkloadManifest.json
   Install Type:              Msi

 [ios]
   Installation Source: VS 18.5.11626.173
   Manifest Version:    26.2.10217/10.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.ios\26.2.10217\WorkloadManifest.json
   Install Type:              Msi

 [wasm-tools]
   Installation Source: VS 18.5.11626.173
   Manifest Version:    10.0.105/10.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.workload.mono.toolchain.current\10.0.105\WorkloadManifest.json
   Install Type:              Msi

 [android]
   Installation Source: VS 18.5.11626.173
   Manifest Version:    36.1.43/10.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.android\36.1.43\WorkloadManifest.json
   Install Type:              Msi

 [maccatalyst]
   Installation Source: VS 18.5.11626.173
   Manifest Version:    26.2.10217/10.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.maccatalyst\26.2.10217\WorkloadManifest.json
   Install Type:              Msi

Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
  Version:      10.0.5
  Architecture: x64
  Commit:       a612c2a105

.NET SDKs installed:
  8.0.419 [C:\Program Files\dotnet\sdk]
  10.0.201 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.25 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 10.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.25 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 10.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 8.0.25 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.14 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 10.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Anything else?

PS>  aspire --version
13.2.1+14bf8c40443c690189a82ecb6565edb91dadf3b1

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions