I have been experimenting with Blazor Web Assembly (WASM) which at the time of writing is in preview for ASP.NET Core 3.1. Here are some quick tips and things to watch out for.
Debugging WASM doesn’t work (in firefox)
The team recently shipped Blazor WASM debugging support. I followed the excellent debugging documentation but couldn’t get it to work. The solution was to pay more attention to the documentation: debugging does not work in Firefox (version 75), as per the documentation specifically the prerequisites
Debugging is only supported in Chromium based browsers.
Debugging requires either of the following browsers: Microsoft Edge (version 80 or later) or Google Chrome (version 70 or later)
Data Annotations not validating all properties
Again the validation documentation is excellent and this specifically calls it out:
Blazor provides support for validating form input using data annotations with the built-in DataAnnotationsValidator. However, the DataAnnotationsValidator only validates top-level properties of the model bound to the form that aren’t collection- or complex-type properties.
To validate the bound model’s entire object graph, including collection- and complex-type properties, use the ObjectGraphDataAnnotationsValidator provided by the experimental Microsoft.AspNetCore.Components.DataAnnotations.Validation package
InputSelect can only bind to string and enum types
I unsuccesfully tried to bind my InputSelect select list to an integer. After a bit of research I found Steve Sanderson address this in this GitHub Issue commment. I adopted this approach and here is my implementation.
Hosting statically on GitHub Pages fails with “Failed to find a valid digest in the ‘integrity’ attribute”
I followed Andrea Cirioni’s blog on Hosting Blazor WebAssembly app on GitHub Pages. This worked great except when I was done, I was seeing the following error:
Failed to find a valid digest in the ‘integrity’ attribute for resource ‘https://palmerandy.github.io/Running-Pace-Calculator/_framework/wasm/dotnet.3.2.0-preview3.20168.1.js' with computed SHA-256 integrity ‘xxx/yyyy=’. The resource has been blocked.
After researching a while, I stumbled across this GitHub Issue and solution from Steve Sanderson. TLDR: I copied Steve’s .GitAttributes file, and added it to my Git repository with the following command:
git add --renormalize .