Activities of "improwise"

yes !!! its working now
pff lost more then 1 week of developing due to this bug :-(

Glad you got it working, we also lost a lot of time on this and had to figure out ourselves how to find a workaround. Not optimal that a commercial product has to rely on customer helping out each other to get things working. It has us considering our options going forward as we are not really happy with how things have turned out recently and we are somewhat worried where things are heading in the future based on this. Let's hope that it is because of all attention being on the 5.0 release and that release is stellar...

created a solution based on 4.4.3, after removing and re-installing CLI with version 4.4.3 again.

abp new test_6 -t app-pro -u blazor-server -csf --output-folder C:\Projects\test_6 --mobile none

but still the same problem

what i noticed is that CLI still uses 'using cached template: app-pro, version 4.4.4'

can this be the reason ? how can the cached template be reset/removed ?

You need to specify the -v 4.4.3 option as ABP will always use latest version of packages regardless of CLI version if not. At least that is what we had to do after having figured out ourselves how to produce working ABP Commercial solutions since 4.4.4 was released. You can then add that to ABP Suite manually and CRUD generation etc. seem to work somewhat ok.

I no longer have problems with CLI 5.0.0-rc1, nuget and npms, but I'm on Blazor Server + EfCore Sql Server with VS 2022 17.0.1 since solution is based on .net 6.0

My steps:

1. uninstalled abp e cli (4.4.4 main workstation and 5.0.0-beta3 notebook),
2. install stable (4.4.4)
3. update to pre-release (5.0.0-rc1)

Can confirm that RC1 seem to work better in this regard. Other problems though but that is to be expected on a RC version. The stable version on the other hand should not have these problems and we can't use none stable versions in a real world application. We have given up on ABP 4.4.4 for now as it seems unfixable. Let's hope there is lots of improvement in 5.0 when release...

I have the same problem also !!!!

Is there already a solution for this problem ? this getting really annoying and time consuming.

I always start from a new solution created from abp suite.
I tried already several versions 4.4.3 , 4.4.4 , aswel visual studio 2019 and 2022

Today i also tried version 5.0.0-RC1 (visual studio 2022)

I run the blazor projects as well in chrome, safari, microsoft edge...

Tried it on 3 different laptops. On 2 laptops i have local admin rights (but the pc is moderated by my customer/company), On my personal laptop , i have all rights. But doesn't seem to make any difference.

I can always build / run complete solution. Also the initial database migration works with DBMigration

And I always get the same error

Important info : the same solution/project runs without any problem for my fellow developer (located in Pakistan, i'm lcoated in europe)

I'm really stuck and i lost already a week finding a solution ....

We moved from the asp.net zero framework to abp.commercial for the blazor support, but I'm getting the feeling that this what not a good move !!!!

Please help

It seems like everyone is able to reproduce this problem with the exception of ABP Support...

The solution, or rather workaround, it to create a solution based on 4.4.3 until ABP fixes this problem. Please note that this requires using the CLI as mentioned elsewhere as ABP will always use latest packages regardless of version it seems.

Please have your Pakestanian friend try a clean and rebuild in VS2022 and let us know if it still works for him/her. Also, can he compile the solution in VS2019?

I've read the thread and couldn't find the message that successfuly reproduced the issue. @EngincanV stated that he could successfully created an entity without any problem.

Then, I could successfully generate CRUD pages for my Book entity.

Again detailed reproduce steps is always helpful for the solution.

Yes, I reproduced this problem using VS 2022. But there is not any problem, when using dotnet run command or using other IDE such as Rider. There could be a problem in VS 2022, we will investigate this, thanks.

The problem here is that the solutions produced by ABP Suite 4.4.4 won't build in VS2019 and won't run in VS2022. And based on what is written here in the support forum, several customers are experiencing the same problem(s). All the information needed to reproduce this problem is already available in the forum and we have already sent you a SLN produced by ABP Suite that shows the problem.

We seem to be stuck in a discussion if the problem(s) exist(s) or not and not moving closer to a solution to them...

Edit: I see that a 5.0 RC1 just got released which is reported to work with VS2022, hopefully those fixes will transition to the 4.4 branch as well.

Pls ensure that your ABP version and your project version is the same! Because we couldn't reproduce the issue.

Note that detailed reproduce steps is always helpful for the solution.

Note sure what you could not reproduce as you colleague said above that he/she could reproduce it and several other customers have confirmed having the same problems as us with 4.4.4?

We have already downgraded everything to 4.4.3 ourselves currently which is working fine.

be sure that you have installed ABP Suite v4.4.4

To us, that didn't make a difference as ABP Suite will use latest packages regardless. What we had to do was to create the solution manually using the CLI and specifying the version as 4.4.3, and then add it manually to ABP Suite.

I would imagine that you probably do not need to downgrade ABP Suite and CLI to 4.4.3 if you only make sure to reference 4.4.3 packages instead of 4.4.4, but we never tried that. My guess is that the Lepthon theme in 4.4.4 is causing these problems but once we got 4.4.3 to work, we have not done any more error searching.

For anyone struggling with this, you need to use the CLI like (written from memory so could be errors)

abp new myproject -t abp-pro -u blazorXXX -v 4.4.3

which would create a new project an reference 4.4.3 packages instead (ABP Suite will always use latest packages it seems regardless of version when you create the project from there). Then you can add that to ABP Suite and use it as normal and it will compile fine with both VS2019 and VS2022 and also work runtime. At least it did for us.

I hope you manage to find a solution to this quickly. Thanks.

Hi @improwise, I've created an app-pro template with Blazor Server as UI and EF-Core as the database provider (in v4.4.4). Then, I could successfully generate CRUD pages for my Book entity.

• Can you check your both application version and suite version is same and in v4.4.4?

For some strange reason, we notice that the error messages seem to be truncated.

Yes, I reproduced this problem using VS 2022. But there is not any problem, when using dotnet run command or using other IDE such as Rider. There could be a problem in VS 2022, we will investigate this, thanks.

Glad to see this issue getting some attention now and hopefully it would then be solved quickly.

Even if it works outside of Visua Studio, that isn't really a viable solution to the problem at hand here but it might give some valuable information to what needs to be fixed. Please note that after downgrading to 4.4.3, everything seems to be back to normal, we tried that ourselves to try to decide if ABP or VS/.net was the problem here. I would imagine that perhaps ABP Suite can still generate CRUD pages, we never tried that since the solution produced by ABP Suite did not work at all reliably.

please provide us the following steps to reproduce your issue

• Your ABP version:
• DB provider: EF Core / MongoDB
• Which template are you having issue? (app-pro , module-pro, console , etc..)
• Tiered or non-tiered
• UI type: Blazor Server / Blazor WASM
• Steps to reproduce the issue:

I believe all needed information is already listed in the OP here and in other threads.

I have the same issue, with all combination of CLI & nuget 4.4.4 / 5.0.0-beta3 on Blazor Server with EfCore. 1st run all is ok
2nd run error and log truncated: Unhandled exception in circuit '1p-8ASDVzLQleQfw2SNY1-9IQo226k0XJ5M-bbKlSC4'. Volo.Abp.AbpException: Undefined permission: AuditL

Undefined permission can be different on each run, and this appen only if there is an instance of browser left open

Just to clarify, this is what we are seing also. That if you manage to compile it, it seem to work first time but then not again. I think that when we messed around with it a bit, we got some idea that it could be related to if you were authenticated or not and that clearing cookies could sometimes have an effect. But if that was some random thing or not we never managed to figure out before we gave up and downgraded to 4.4.3.

I do believe that we can say that enough users are affected by this in some way or another so that we can conclude that it is an actual real problem with ABP 4.4.4 / and beta 5 and not just something related to bad configuration on a single development machine etc. And since everything seem to work fine when you downgrade to 4.4.3 (at least it seems to do for us), I guess it is unlikely that it is due to problems with VS2022 or .net 5/6 even though you can of course never be sure.