We are on the verge of releasing our first Blazor WebAssembly stand alone (i.e. not hosted on .Net Core) app. I've come to love Blazor and look forward to producing some great apps with it! However pushing app updates has been a headache! There seems to be a persistent cache that is hard to update and it is super annoying! Likely it is my lack of understanding but it does not seem to work like everyone says it should.
I would like to build some kind of app versioning system and a way to notify users that an update is available. Most important of all I would like to give users the ability to manually perform an update... but searching for this topic has been difficult. I must not be using the right keywords as there seems to be no documentation on this for Blazor?
If I leave Blazor out of my search query it seems that other SPA applications do this via the Service Worker if I am understanding it correctly? However this is a whole other deep subject into itself and apparently something that I will have to learn if my understanding is correct?
Can anyone lead me in the right direction in how I can learn about creating such an update process?
