Activities of "improwise"

ABP Framework version: v4.4.4 UI type: Blazor Server DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no

This line seem to appear in the obj/debug after having built a new Blazor server project created with ABP Suite in combination with an error which make the project not compile

#line (1,31)-(1,48) 24 "M:\Projects\ASP.NET\ABP\src\TEST1\aspnet-core\src\TEST1.Blazor\Components\Layout\MainFooterComponent.razor"

In VS2022 (both Preview and Current) the project seem to compile fine though, so not sure if this is an ABP problem or a Microsoft problem. All updated available to VS, .net etc have been installed.

Please have a look in the bug thread for 4.4.4 (isn't anyone from Volo reading that?) for my posts about what seems to be a very similar problem, newly created project with ABP Suite don't work because of missing permissions as well.

https://support.abp.io/QA/Questions/1543/Bugs--Issues-v44X

Short version, Blazor (client and server) seem to be broken currently even if you create a new project with default settings in ABP Suite and just try to run it after having executed DBMigrator.

ABP Framework version: v4.4.4 UI type: Blazor Server DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no

After upgrading to ABP 4.4.4 we can no longer create working projects in ABP Suite (have no tried other methods). The DBMigrator runs fine on a newly created project (default options, .net 5, no preview) but at runtime we get

[17:46:09 INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement

[17:46:10 WRN] Unhandled exception rendering component: Undefined permission: Audit Volo.Abp.AbpException: Undefined permission: Audit

and in the browser:

blazor.server.js?_v=637706942980000000:21 [2021-11-10T16:46:09.985Z] Error: There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions by setting 'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'.

We have also since last time we tried using ABP Suite upgraded from VS2022 Preview to Current, but I don't think that is the cause of the problem here. Could possibly be related to .net updates also.

Tried creating a project from the website and that seem to work, so only Commercial projects seem to be affected by this, so guessing maybe it is related to Lepton theme or something like that. MVC project seem to work find when created via ABP Suite but neither of the blazor templates seem to do.

Edit:

We tried to downgrade CLI and ABP Suite to 4.4.3 but that didn't change anything, maybe because it seems that they will still use ABP 4.4.4. packages in the created solution.

I hope that this can be fixed ASAP as it is currenlty impossible to create new working projects using blazor in ABP Suite it seems.

Edit 2:

This seem to be a repeating problem, we also see simliar errors like:

[13:45:21 ERR] Unhandled exception in circuit 'sF6jaNnBmq7Uz9BlWzCUc5UsyUK3S_RpvfUdCytjBok'. Volo.Abp.AbpException: Undefined permission: AbpId?

Edit 3:

Downgrading to 4.4.3 solved the problem kind of, but since ABP Suite always seem to default to latest packages, we had to create a new project with -t abp-pro -u blazor-server -v 4.4.4 and then add that to ABP Suite for it to work. If not, you still get the 4.4.4 packages even if ABP Suite and CLI installed is 4.4.3 it seems.

ABP Framework version: v4.4.4 UI type: Blazor Server DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no

After upgrading to ABP 4.4.4 we can no longer create working projects in ABP Suite (have no tried other methods). The DBMigrator runs fine on a newly created project (default options, .net 5, no preview) but at runtime we get

[17:46:09 INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement

[17:46:10 WRN] Unhandled exception rendering component: Undefined permission: Audit Volo.Abp.AbpException: Undefined permission: Audit

and in the browser:

blazor.server.js?_v=637706942980000000:21 [2021-11-10T16:46:09.985Z] Error: There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions by setting 'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'.

We have also since last time we tried using ABP Suite upgraded from VS2022 Preview to Current, but I don't think that is the cause of the problem here. Could possibly be related to .net updates also.

When trying to create a new solution using ABP Suite we get:

Error occured while getting the latest version from https://abp.io/api/download/template/get-version/ : Remote server returns '500-Internal Server Error'. Message: An internal error occurred during your request! [12:56:10 ERR] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "An internal error occurred during your request!", "details": null, "data": {}, "validationErrors": null }

Creating a new solution with same setup via abp.io (Community) seem to work.

ABP Framework version: v4.4.2 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no

Exception message and stack trace: The project name is invalid! Please specify a different name. Volo.Abp.Cli.CliUsageException: The project name is invalid! Please specify a different name.

Steps to reproduce the issue:

It seems like it is impossible to create a new project/SLN in ABP Suite that contains/ends with "Blazor", like "TestProjectBlazor". Generating the project online with the same name and then open it in ABP Suite seem to work though. No problem creating something like "TestProjectAngular".

• at Volo.Abp.Cli.Commands.NewCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\NewCommand.cs:line 66 at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SolutionService.CreateSolutionAsync(CreateSolutionModel input) at lambda_method2438(Closure , Object ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.

Had a quick look and it seems like there are few resons not to use the ABP Suite instead assuming you have access to it of course.

Hi,

Redis is the most popular cache server. It has undergone a lot of tests and has extremely high performance and stability. so this is why we choose to redis.

Memurai seems good, you can also try to use it, the code does not need any changes, because it is fully compatible with redis

Thank you.

Hi,

To improve performance, we cache permissions and settings etc, so we need distributed caching to keep public and back-end website data consistent.

Thanks, but that isn't really an answer to why the choice was made to go with Redis in particular, just why caching in general is a good thing.

Related question, should we consider using something like Memurai instead which seems to run natively on Windows?

https://www.memurai.com/