Forum Discussion
Blazor WASM PWA – Applications updates, cache busting with notification or force refresh
My team is currently working on a Blazor application and after several bouts of confusion between developers and testers we stuck a version number on the home screen and discovered the updates weren’...
Strange, I did all of this on .NET7 but didn't encounter that error. Just out of interest, could you try a clean and rebuild on that? Wondering if there's some reference to previous dlls that may be able to be cleared.
Yes, Clean and rebuild resolved the issue the first time, but the error appears randomly with new releases. From what I understand, this is a known issue with .dll files, that's why the team decided to rename the binaries to .wasm instead.
Today I was testing with .NET 8 and it seems indeed the problem is solved in .NET 8.
Today I was testing with .NET 8 and it seems indeed the problem is solved in .NET 8.
- Amazing! Thanks for investigating the functionality in .NET8, that was going to be my next move so you've saved me a job there. Glad to know it will be resolved after an upgrade. Fortunately my project isn't going to production till next year and I've planned in a .NET8 migration.