Conversation
Aligns Aspire.AppHost.Sdk with the 13.5.4 Aspire.Hosting packages and suppresses the new ASPIRE010 warning, since the samples keep using the packaged DCP and dashboard rather than the Aspire CLI bundle.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 49 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closing: the local error was a stale database volume, not the SDK version. Versions will be aligned in a separate PR. |
Coverage Report for CI Build 36724800185Coverage increased (+0.3%) to 89.045%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Summary
Aspire.AppHost.Sdkfrom 13.4.6 to 13.5.4 in both sample AppHosts (samples/Aspireandsamples/DistributedAspire), matching theAspire.Hosting.*13.5.4 packages already pinned inDirectory.Packages.props.ASPIRE010, which the 13.5 SDK emits because it defaultsAspireUseCliBundletofalse. The samples keep using the packaged DCP and dashboard, so they don't need the Aspire CLI installed. Enabling the bundle can happen in a separate change.Testing
samples/Aspire/AppHost(net10.0) locally: the dashboard came up on :15888 and it logged "Distributed application started".