⚡ Update ABP CLI and ABP Suite
dotnet tool update -g Volo.Abp.Cli --prerelease
abp suite update --preview
📗 Blog post
- https://blog.abp.io/abp/announcing-abp-8-2-release-candidate
📘 Commercial release logs
- https://docs.abp.io/en/commercial/8.2/release-notes
- https://commercial.abp.io/releases/
🔼 Migration guides
- https://docs.abp.io/en/abp/8.2/Migration-Guides/Abp-8_2
- https://docs.abp.io/en/commercial/8.2/migration-guides/v8_2
✏️ Feel free to report any bugs, issues, and problems.
137 Answer(s)
-
0
It seems like the new "Blazor Web App" alternative no longer has an option for PWA like the Blazor WASM and Blazor Server alternatives?
-
0
When you run the HttpApi.Host you get this screen, where I assume you are supposed to be able to click the Swagger icon to actually get to the Swagger definition instead of having to type /swagger, but this does not work. Does not work with previous ABP non RC version either.
-
0
Hello!
Newest Blazor WebApp template doesn't render correctly the style of the scrollbar
-
0
You can't create an entity with ABP Suite + ABP Cli 8.2.0-rc.3
-
0
is ABP commercial using Blazorise Free tier? it's showing a message to purchase commercial version
-
0
DateOnly new type is not displaying any control or component to change it's data in Blazor WebApp new template
-
0
In Blazor WebApp, if you click on "Actions" and then click on "Edit", it will also trigger the delete checkbox. If you try to edit more than one row, it will check both of them, that does not seem like the expected behavior.
-
0
It seems like the new "Blazor Web App" alternative no longer has an option for PWA like the Blazor WASM and Blazor Server alternatives?
Yes, currently there is no PWA option for the Blazor Web App.
-
0
In Blazor WebApp, if you click on "Actions" and then click on "Edit", it will also trigger the delete checkbox. If you try to edit more than one row, it will check both of them, that does not seem like the expected behavior.
Unfortunately, this is related to the DataGrid component of Blazorise. We have an internal issue for this limitation and when it's supported by Blazorise, we will make the related changes on our side.
-
0
I have created a new Blazor Web App project in ABP Suite using 8.2.0-rc.3. I periodically get this message when starting the project. Refreshing the page fixes the problem and I can carry on.
Microsoft.AspNetCore.Http.DefaultHttpContext.get_User() Volo.Abp.AspNetCore.Security.Claims.HttpContextCurrentPrincipalAccessor.GetClaimsPrincipal() Volo.Abp.Security.Claims.CurrentPrincipalAccessorBase.get_Principal() Volo.Abp.Authorization.Permissions.PermissionChecker.IsGrantedAsync(string[] names) Volo.Abp.Authorization.Permissions.RequirePermissionsSimpleBatchStateChecker.IsEnabledAsync(SimpleBatchStateCheckerContext context) Volo.Abp.SimpleStateChecking.SimpleStateCheckerManager.IsEnabledAsync(TState[] states) Volo.Abp.UI.Navigation.MenuManager.CheckPermissionsAsync(IServiceProvider serviceProvider, IHasMenuItems menuWithItems) Volo.Abp.UI.Navigation.MenuManager.GetInternalAsync(string name) Volo.Abp.UI.Navigation.MenuManager.GetAsync(string[] menuNames) Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Navigation.MainMenuProvider.GetMenuAsync() Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.SideMenu.MainHeader.MainHeader.OnInitializedAsync() Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync() Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState) Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState) Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.g__Execute|38_0() Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.WaitForResultReady(bool waitForQuiescence, PrerenderedComponentHtmlContent result) Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.RenderEndpointComponent(HttpContext httpContext, Type rootComponentType, ParameterView parameters, bool waitForQuiescence) System.Threading.Tasks.ValueTask.get_Result() Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context) Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context) Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext+<>c+<b__10_0>d.MoveNext() Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|7_0(Endpoint endpoint, Task requestTask, ILogger logger) Volo.Abp.AspNetCore.Serilog.AbpSerilogMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.Auditing.AbpAuditingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Volo.Abp.AspNetCore.Auditing.AbpAuditingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider) Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) Volo.Abp.AspNetCore.Security.Claims.AbpDynamicClaimsMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.Uow.AbpUnitOfWorkMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.ExceptionHandling.AbpExceptionHandlingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Volo.Abp.AspNetCore.ExceptionHandling.AbpExceptionHandlingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.MultiTenancy.MultiTenancyMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Builder.ApplicationBuilderAbpOpenIddictMiddlewareExtension+<>c__DisplayClass0_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) Volo.Abp.AspNetCore.Security.AbpSecurityHeadersMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.Tracing.AbpCorrelationIdMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context) Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
-
1
I have created a new Blazor Web App project in ABP Suite using 8.2.0-rc.3. I periodically get this message when starting the project. Refreshing the page fixes the problem and I can carry on.
Microsoft.AspNetCore.Http.DefaultHttpContext.get_User() Volo.Abp.AspNetCore.Security.Claims.HttpContextCurrentPrincipalAccessor.GetClaimsPrincipal() Volo.Abp.Security.Claims.CurrentPrincipalAccessorBase.get_Principal() Volo.Abp.Authorization.Permissions.PermissionChecker.IsGrantedAsync(string[] names) Volo.Abp.Authorization.Permissions.RequirePermissionsSimpleBatchStateChecker.IsEnabledAsync(SimpleBatchStateCheckerContext context) Volo.Abp.SimpleStateChecking.SimpleStateCheckerManager.IsEnabledAsync(TState[] states) Volo.Abp.UI.Navigation.MenuManager.CheckPermissionsAsync(IServiceProvider serviceProvider, IHasMenuItems menuWithItems) Volo.Abp.UI.Navigation.MenuManager.GetInternalAsync(string name) Volo.Abp.UI.Navigation.MenuManager.GetAsync(string[] menuNames) Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Navigation.MainMenuProvider.GetMenuAsync() Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.SideMenu.MainHeader.MainHeader.OnInitializedAsync() Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync() Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState) Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState) Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.g__Execute|38_0() Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.WaitForResultReady(bool waitForQuiescence, PrerenderedComponentHtmlContent result) Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.RenderEndpointComponent(HttpContext httpContext, Type rootComponentType, ParameterView parameters, bool waitForQuiescence) System.Threading.Tasks.ValueTask.get_Result() Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context) Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context) Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext+<>c+<b__10_0>d.MoveNext() Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|7_0(Endpoint endpoint, Task requestTask, ILogger logger) Volo.Abp.AspNetCore.Serilog.AbpSerilogMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.Auditing.AbpAuditingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Volo.Abp.AspNetCore.Auditing.AbpAuditingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider) Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) Volo.Abp.AspNetCore.Security.Claims.AbpDynamicClaimsMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.Uow.AbpUnitOfWorkMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.ExceptionHandling.AbpExceptionHandlingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Volo.Abp.AspNetCore.ExceptionHandling.AbpExceptionHandlingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.MultiTenancy.MultiTenancyMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Builder.ApplicationBuilderAbpOpenIddictMiddlewareExtension+<>c__DisplayClass0_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) Volo.Abp.AspNetCore.Security.AbpSecurityHeadersMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Volo.Abp.AspNetCore.Tracing.AbpCorrelationIdMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context) Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+InterfaceMiddlewareBinder+<>c__DisplayClass2_0+<b__0>d.MoveNext() Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
Can confirm that I have the same problem and same solution. Not sure if it is .NET or ABP releated though, this new Blazor WebApp seems a bit shaky overall.
-
0
On a new Blazor Web App project in ABP Suite using 8.2.0-rc.3.
On starts up it looks like the Side Menu is available before it is ready.
If a menu item is clicked before the browser loading spinner stops the menu gets stuck/confused.
It is easily replicated by F5 page refresh, then click on a menu item before the browser spinner stops.
I noticed this when the MyFooter override text does not always displayed. Often it shows the default Lepton text - but other times it is the MyFooter text.
---- SOLVED Added a pages folder to the Blazor project (not the .Client one) and added the same MyFooter.razor
Problem solved.
-
0
On a new Blazor Web App project in ABP Suite using 8.2.0-rc.3.
When Exceptions are raised the message dialog appears ok, but after clicking ok, the page reverts to the base URL.
It is easy to replace by raising and exception on any Create or Edit modal.
--- UPDATE This only occurs when: <Routes @rendermode="InteractiveWebAssembly" /> and <Routes @rendermode="InteractiveAuto" />
When in <Routes @rendermode="InteractiveServer" /> the exceptions behave as normal.
-
0
Is it possible to generate non RC solutions from ABP Suite with the RC CLI and Suite installed or do you have to downgrade? There is a "Preview" checkbox in the ABP Suite but it is not quite clear what it actually does and if it does anything since the ABP Suite itself is preview.
Mainly asking as it would be easier when you find bugs etc with RC versions if you could compare it easily with a non RC solution to see if it is new bugs of maybe have been around before as well. Would probably be helpful for Volosoft also to know.
-
0
Since there are many reports here about Blazor WebApp bugs, do we have a feeling on how stable they are in general, ie outside of ABP? I have experimented a bit with the new Blazor WebApp in VS and find that it still isn't really stable in itself, especially with regards to render modes (mainly the Auto one).As always, it is a bit tricky to know if bugs you encounter are ABP RC related or maybe Microsofts fault.
-
0
Is it possible to generate non RC solutions from ABP Suite with the RC CLI and Suite installed or do you have to downgrade? There is a "Preview" checkbox in the ABP Suite but it is not quite clear what it actually does and if it does anything since the ABP Suite itself is preview.
Mainly asking as it would be easier when you find bugs etc with RC versions if you could compare it easily with a non RC solution to see if it is new bugs of maybe have been around before as well. Would probably be helpful for Volosoft also to know.
you can create a specific ABP version project, see https://docs.abp.io/en/abp/latest/CLI-New-Command-Samples#create-a-solution-from-a-specific-version
-
0
Is it possible to generate non RC solutions from ABP Suite with the RC CLI and Suite installed or do you have to downgrade? There is a "Preview" checkbox in the ABP Suite but it is not quite clear what it actually does and if it does anything since the ABP Suite itself is preview.
Mainly asking as it would be easier when you find bugs etc with RC versions if you could compare it easily with a non RC solution to see if it is new bugs of maybe have been around before as well. Would probably be helpful for Volosoft also to know.
you can create a specific ABP version project, see https://docs.abp.io/en/abp/latest/CLI-New-Command-Samples#create-a-solution-from-a-specific-version
And that will work with a RC version of the CLI installed as well? And you will be able to open that generated solution in the RC version of ABP Suite and then use it as with a non RC version?
-
0
hi @cellero @improwise
I have created a new Blazor Web App project in ABP Suite using 8.2.0-rc.3. I periodically get this message when starting the project. Refreshing the page fixes the problem and I can carry on.
I will confirm this problem. Thank your for your feedback.
https://github.com/abpframework/abp/issues/19971
-
0
hi @cellero @improwise
I have created a new Blazor Web App project in ABP Suite using 8.2.0-rc.3. I periodically get this message when starting the project. Refreshing the page fixes the problem and I can carry on.
I will confirm this problem. Thank your for your feedback.
Could be a coincidence but I get the feeling that you need to run it once without debugging, then it will work to run with debugging. Have not done any systematic testing of it though.
-
0
Thanks improwise
-
0
Unless it is already mentioned, it should probably be mentioned in the documentation that Blazor apps created using the new WebApp template by default get Auto rendermode
<AbpStyles BundleName="@BlazorLeptonXThemeBundles.Styles.Global" WebAssemblyStyleFiles="GlobalStyles" @rendermode="InteractiveAuto" />Perhaps there should also be options in ABP Suite to select what you want like in VS, but perhaps that is something for the developer to change in code instead if needed.
-
0
You can't create an entity with ABP Suite + ABP Cli 8.2.0-rc.3
Can confirm this problem, which basically means that you can only use ABP Suite in RC3 to create new solutions as this error aborts any additional code generation it seems.
Edit:
Can add that this problem seems to be only related to the new Blazor WebApp, when creating a Blazor Server solution with ABP Suite, it seems to work as it should.
-
0
What exactly does this option do/change and what will happen if you unselect it?
Was some time ago that I used the ABP Suite in RC version so not sure if that checkbox has been around for a while now.
-
0
Seems like the MAUI template needs updating
Maui\Extensions\MarkupExtensionBase.cs(9,13,9,45): warning CS0618: 'MauiApplication.Services' is obsolete: 'Use the IPlatformApplication.Current.Services instead.' -
0
When creating a Blazor solution also containing a MAUI project, when you try to login in the running MAUI app, you will be redirected to a login page in the web browser. The login itself seem to work find but the login page in the browser never seem to update to the usual "Authentication completed, you can now close this window and return to the app" or something like that but instead will just continue to show the login screen. This is running locally as I windows app I might add, could be different on Android, iOS etc.
This is how the web page looks even though login has been completed successfully.
