Move aspire to toolset. (#18428)

This commit is contained in:
Matt Mitchell 2024-01-26 14:48:02 -08:00 committed by GitHub
parent af3c100f01
commit 7a9c02da61
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -174,11 +174,6 @@
<Sha>ae7c93e25ae596594b3b22d64115f374a3595912</Sha>
<SourceBuild RepoName="emsdk" ManagedOnly="true" />
</Dependency>
<Dependency Name="Microsoft.NET.Sdk.Aspire.Manifest-8.0.100" Version="8.0.0-preview.3.24060.4">
<Uri>https://github.com/dotnet/aspire</Uri>
<Sha>66a1dd77e4077592a587c1429c8814d1057dc474</Sha>
<SourceBuild RepoName="aspire" ManagedOnly="true" />
</Dependency>
<Dependency Name="Microsoft.Deployment.DotNet.Releases" Version="2.0.0-preview.1.24067.1" CoherentParentDependency="Microsoft.NET.Sdk">
<Uri>https://github.com/dotnet/deployment-tools</Uri>
<Sha>e56c69b0610b50407d29fdc2dda2574712a7b94d</Sha>
@ -245,5 +240,17 @@
<Sha>bfde902a10d7b672f4fc7e844198ede405dbb9c6</Sha>
<SourceBuild RepoName="scenario-tests" ManagedOnly="true" />
</Dependency>
<!-- Aspire isn't really a toolset dependency. However, it only inserts a baseline manifest in installer,
and if you squint at it, this means we can say that its specific dependency versions don't matter to installer.
Avoiding this as a product dependency avoids a long coherency path (aspnetcore->extensions->aspire->installer).
**It is** of course possible that an incoherent aspire means that aspire depends on versions of extensions that
aren't shipping, or those extensions packages depend on aspnetcore packages that won't ship. However, given the cost
of maintaining this coherency path is high. This being toolset means that aspire is responsible for its own coherency.
-->
<Dependency Name="Microsoft.NET.Sdk.Aspire.Manifest-8.0.100" Version="8.0.0-preview.3.24060.4">
<Uri>https://github.com/dotnet/aspire</Uri>
<Sha>66a1dd77e4077592a587c1429c8814d1057dc474</Sha>
<SourceBuild RepoName="aspire" ManagedOnly="true" />
</Dependency>
</ToolsetDependencies>
</Dependencies>