Move integrity support to the Static Web Assets SDK from the Blazor WebAssembly SDK

[javiercn]

We do have a set of features for dealing with hashes ("integrity") on Blazor files as well as for applying fingerprints to files, we should move those to static web assets.

• We will add two new properties to the definition of a static web asset "Fingerprint" and "Integrity".
  • Fingerprint is the Base36 encoding of the integrity hash that can be used to uniquely fingerprint the file.
  • Integrity will be the Base64 encoding of the SHA256 hash, which is what we currently put in the blazor.boot.json manifest.
• We will update DefineStaticWebAssets to automatically compute the fingerprint and hash for the assets being defined.
  • The way I envision this working is via "token" replacements. We can support defining tokens in the file name, like asset.[Fingerprint].razor.js.
  • When we are constructing the asset relative path, we replace the [Fingerprint] bit with the actual computed fingerprint of the asset, which is stored in item metadata for the item.
  • We make comparisons based on the relative path and other aspects, so we might need a property separate from the relative path (RelativePathTemplate) or similar to make it easier to work.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Bartmax]

As stated on this issue #49809 updating the server files every time one needs to publish a new version is not really a viable workaround, hope we get some options sooner rather than later.

If there are any other option that I may be missing please that would be very useful in the meantime.

Thanks.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[javiercn]

This was done as part of the WebAssembly fingeprinting integration.