SDK product construction is broken when aspnetcore moves ahead of runtime #47070
Labels
Comments
dotnet-issue-labeler
bot
added
Area-NetSDK
untriaged
1 task
|
What's the status here? Is progress being made towards a fix? |
|
We fixed this for a single point in time so that we could promote a newer SDK to Arcade but this issue tracks investigating why tests didn't fail when there's the coherency mismatch between aspnetcore and runtime. While the overall problem will go away with the VMR, we still should have tests that asset the expected state. |
|
We had a test in installer that caught this there but when run in sdk, it's apparently not catching it. is it a problem with our stage 2 setup maybe? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the main SDK has a newer aspnetcore which itself references a newer runtime than what's inserted into sdk.
IOW:
sdk -> aspnetcore -> runtime (newer)
sdk -> runtime (older)
Customer Impact: Using
Microsoft.AspNetCore.App(aspnetcore) is broken. The host fails to load apps that depend on it.I thought we had tests for that...
The text was updated successfully, but these errors were encountered: