Activities of "AndrewT"

The main problem is the information in the error message is not helpful.

so that is the first thing to resolve.

We do not want to download and edit source as that will then be a problem when we have to upgrade eg 4.3 patch.

bump

@liangshiwei Thanks, we'll try that I really hope you can get this framework faster, we would have to change lots of things to migrate back to a Server. I already discussed that in a different question and Alpers said we had to create a brandnew tenmplate and t5hem migrate the whole app piece by piece over...

• ABP Framework version: v4.3
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes / no
• Exception message and stack trace:
• Steps to reproduce the issue: example below where user connection is lost and what they need to do is login again.

How can we improve the error messages like this one, which is not helpful for a user, without having to edit the source because that breaks the ability to easily upgrade.

@liangshiwei - As you know the Blazor WASM is dreadfully slow to load. It takes 10+ seconds. The user experience is made worse by having to go to the index page. GTMetrix even times out on the first page load time!

How do we;

1. Display a loading indicator so the user knows something is actually happening.
2. Go straight to the Login page. Having to do a redirect from another page we don't want just to get to the login is crazy, and adds moire user frustration.

We also dont want to have to mess with the module source code for something so obvious as that then breaks the ability to easily upgrade.

Really appreciate your help here, these are basic and reasonable requirements for a framework.

@mladen.macanovic we had already upgraded to v4.3-RC WASM. What is required to go from 4.3 WASM to 4.3 Server?

@BassaSolutions - could you update later on your experience with 4.3 Server?

The performance is so bad we also feel stuck and are unsure about continuing the migration of other apps from aspnetzero.

What is required and the effort to migrate a blazor app from WASM back to a server side app? We are also finding the performance incredibly bad. Also WASM is single threaded so we expect issues with trying to run parallel processes, eg Audio and UI.

would be great to also include the integration with Stripe and Xero, so the whole billing payment cycle is clean and working out of the box.

Edition charge Units used (txt, space, users, records, etc).

@Alper - when is the next RC?

next week

@Alper - When it is final release? How can we get email working with longe keys in Blazor before then?

@Alper - when is the next RC?