I would be very interested to hear any feedback on this issue my self!
I find it very strange that nobody can comment on them other than “its jus Blazor and abp is bringing lot to the table” so this is just normal.
There is nothing normal about this load time at all!
Btw I would think about using static web application and CDN to distribute your app! We got our loading time from 50-60 sek (!!) to 10-15 sek after compression finally worked.
Compression did only work in version 6.0…1.5 years after Blazor WASM was released…
We managed to figure this out and it was our fault and now everything loads just fine so closing this issue!
So, is this a bug in 6.0.1 and is there a workaround or do we need to wait for next patch?
Thank you, its Sturla@ibeinni.is
Did you see the answer Liangshiwei? https://github.com/abpframework/abp/pull/13772
If I add the .br statement to the web .config file for my abp.io project I just get the error you can see in my answer https://github.com/abpframework/abp/pull/13772#issuecomment-1324630884.
Can you get this to work on your side? I´m VERY apprehensious to get this into next 6.0 patch if there is any change needed on your side.
I asked this question at aspnetcore. Please add more details to it if you feel I´m missing something so we can get the proper help from them to fix this.
Hi, I answered back since I´m not getting this to work, see here.
I've reproduced this problem recently
My issue or Mateworkx's one?
p.s sorry for hijacking your issue Mateworkx
Hi, can you run the abp bundle command in your Blazor project and then re-run the project?
EngincanV we are having his issue here https://support.abp.io/QA/Questions/3868/Issue-logging-into-Blazor-WASM-only-on-Azure-after-updating-to-60-and-migrating-to-opendict
Could it be we need to run abp bundle in our pipeline? Everything works fine in local development!