Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Aspire Orchestration Causes Errors When Using Directory.Packages.props #1253

Closed
ardalis opened this issue Dec 6, 2023 · 1 comment

Comments

@ardalis
Copy link

ardalis commented Dec 6, 2023

Add support for solutions using:

    <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>

and Directory.Packages.props files. Currently when adding Aspire Orchestrator Support to an existing web app you get this error:

Severity Code Description Project File Line Suppression State
Error NU1008 Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: OpenTelemetry.Instrumentation.AspNetCore;OpenTelemetry.Instrumentation.GrpcNetClient;OpenTelemetry.Exporter.OpenTelemetryProtocol;OpenTelemetry.Instrumentation.Runtime;Microsoft.Extensions.Http.Resilience;Microsoft.Extensions.ServiceDiscovery;OpenTelemetry.Extensions.Hosting;OpenTelemetry.Instrumentation
ServiceDefaults.csproj 1
and AppHost.csproj (which only has one reference but still includes the version in the csproj file).

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 6, 2023
@tlmii tlmii added area-tooling and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Dec 6, 2023
@DamianEdwards
Copy link
Member

This is an issue for all .NET project templates, not just Aspire, and is being tracked by NuGet at NuGet/Home#12967

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants