Folks, we have an intermittent serious problem with publishing updates to
our Blazor app. I'm hoping someone knows of tricks or techniques to fix it.
When publishing a new version I delete all files from the vdir beforehand,
then I stop+start the Azure app service in an attempt to force the new
version to be visible. However, on the client-side just about anything can
go wrong. We see stalls, absurd JavaScript errors, 3rd party control
licencing errors, 403 file errors, etc. Any stupid thing that can go wrong
probably will. I know the app release is perfectly valid and passes all
tests, but when deployed it goes randomly up sh*t creek for the end user in
the web browser.
I assume the behaviour of web browsers is to blame and we have limited
control over that. Is there some server or client side configuration or
meta that can help avoid this problem? Or some other technique?
We have some large companies using our app and they're getting very
irritated, so any advice would be most welcome.
Thanks,
*Greg Keogh*
