dotnet / dotnet/aspnetcore

[Blazor] WebAssembly package version missmatch with SDK/RuntimePack version

Open
#60,461 6 comments 0 reactions 0 assignees View on GitHub
area-blazor
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 5h
Merged PRs (30d)
276

Description

When upgrading project/application to new TFM, it can happen that we omit to update `Microsoft.AspNetCore.Components.WebAssembly` or `Microsoft.AspNetCore.Components.WebAssembly.DevServer` version that are defined as package reference. In case of servicing release, it may even not be trigger by our action, as for example CI may get different servicing release of SDK.

Possible solutions
1. Define the package references implicitly by the BlazorWasmSDK. This doesn't solve the problem for component libraries
2. Produce a warning/error during build when `RuntimePack` version doesn't match `Components.WebAssembly` or `DevServer` version
3. Use the same approach as WinForms/WPF by having a `UseBlazorWebAssembly` MSBuild property that pulls in `Components.WebAssembly` package reference

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.