This is more or less what happens on local dev:
After hitting that /connect/authorize with 302 status and subsequent login-callback-error, it tries to reload again all the scripts and css that were previously loaded.
Also don't understand why.
What can I share with you guys to help me in this matter?
Tks a lot!
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…
Tks, Sturla. Will also try your suggestions.
Did you encounter those errors what I mentioned above in your implementation?
It seems, as far as I could decipher, that all the idle times are coming from the errors bellow. After each error there is an ~ 10 sec of idle time, then resumes, then another error, another 10 seconds, then finally website loads.
More exactly when it tries to do this:
I don't understand what is happening. API is working perfectly fine.
I have the same error on local dev machine, minus the idle time between them.
What is ABP trying to do? I am using standard Blazor wasm template.
https://github.com/abpframework/abp/issues/13114
See also this, the last week comment. We have the sane situation.
Already did that.
Has nothing to do with idle times. There are literally seconds where nothing happens and it's related to the internals of ABP as I couldn't reproduce this with any other Blazor app.
Please provide some guidance as I can't use the app like this in prod.
Hi @ccernat, We are sorry for the late response.
First of all, please delete this github repository. Your nuget api key is exposed there https://github.com/RelevanceRo/TestChatModule/blob/master/NuGet.Config
This is not allowed.Why the public website is an MVC Razor pages app if the template is Blazor wasm? Is it planned to update the ABP Suite to generate the public website with the same tech stack as the back-end app?
Blazor wasm is for single-page backend applications and not suitable for public websites.
ABP Suite should have an options to disable SaaS / Tenancy from the UI. The SaaS / Tenancy is really a small niche of application developed with ABP Framework.
We may consider disabling multi-tenancy on project creation. I'll create an issue about that.
Why after I disable multitenancy I still get in the Administration menu SaaS / Tenant sections? How can I actually remove completely those sections from the administration menu?
You have to remove the Saas module from the solution (csproj & module.cs files).
We'll reply the question related with Chat module in a short time.
My bad. Repo deleted.
Tks for noticing.
Works perfectly!
Tks alot.
PS. The problem was indeed the placement of the survey.jquery.min.js!
Hello again!
Someone help, please? :)
Tks.
Hello!
Any updates on this?
Thank you.
Solved it. Tks!
