Don't require latest runtime patch for Blazor DevServer #56123
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you have not installed an SDK with the 8.0.6 runtimes, but you reference the 8.0.6 version of the Microsoft.AspNetCore.Components.WebAssembly.DevServer NuGet dependency, you’ll see the following error:
Similar reports come into VS feedback and GitHub pretty regularly with every patch. VS does not seem to give any details other than the following in from the “Debug” output by default.
If you try to
dotnet run
the project, you’ll see the following output:You can work around this issue by installing the 8.0.301 SDK from https://dotnet.microsoft.com/en-us/download/dotnet/8.0 that brings in the 8.0.6 runtime. Or you can downgrade the Microsoft.AspNetCore.Components.WebAssembly.DevServer NuGet dependency to 8.0.5.
However, it ought not be necessary for the NuGet dependency to exactly align with the runtime patch version. dotnet/runtime#88204 (comment) has more context.
I think we should consider backporting at least the first commit to
release/8.0
. The second commit deletesMicrosoftAspNetCoreAppVersion
which was out of date and apparently not used for anything important. @sebastienros I found this reference to BasicApi.csproj in one of our benchmark jobs, but the path is incorrect (it doesn't include the "perf/" directory), so I deleted the outdated PackageReference that was intended to assist with benchmarking. We could put it back but useSharedFxVersion
or something similar if we need it.Fixes #56119