Activities of "Sturla"

I created file new project (that will send you now) where I could reproduce this.

Just navigate between Dashboard and Users few times (3-5x rather fast (doesn´t have to be super fast) and you will see this error

Hi

Do you have a workaround for me or is this a bug and if so will it be fixed in 7.0.2.

Any news on this liangshiwei?

Should be super easy to test on your end and see it fail, that is if its not something else I’m doing wrong (and you can hopefully help me with)

Sorry for the title but I´m unsure what to call this

But if I navigate to and from the user management dropdown (to some other page) I get the following exception with a error message and UI popup.

blazor.webassembly.js:1 
       
 crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: Cannot access a disposed object.
      Object name: 'BSR.Beinni.Blazor.Pages.BsrUserManagement'.
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'BSR.Beinni.Blazor.Pages.BsrUserManagement'.
   at Microsoft.AspNetCore.Components.OwningComponentBase.get_ScopedServices()
   at Volo.Abp.AspNetCore.Components.AbpComponentBase.LazyGetRequiredService[IObjectMapper](Type serviceType, IObjectMapper& reference)
   at Volo.Abp.AspNetCore.Components.AbpComponentBase.get_ObjectMapper()
   at Volo.Abp.Identity.Pro.Blazor.Pages.Identity.UserManagement.GetOrganizationUnitsAsync(ICollection`1 selectedOuIds)
   at Volo.Abp.Identity.Pro.Blazor.Pages.Identity.UserManagement.OnInitializedAsync()
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

Here is the code

namespace BSR.Beinni.Blazor.Pages
{
    [ExposeServices(typeof(UserManagement))]
    [Dependency(ReplaceServices = true)]
    public class BsrUserManagement : UserManagement
    {
        protected override async ValueTask SetEntityActionsAsync()
        {
            await base.SetEntityActionsAsync();

            var indexClaim = EntityActions.Get<UserManagement>().FindIndex(x => x.Text == "Claims");
            EntityActions.Get<UserManagement>().RemoveAt(indexClaim);
        }
    }
}

I thought this might be related to Use Default ComponentActivator for Blazorise

so I added this

context.Services.Replace(ServiceDescriptor.Scoped<IComponentActivator, ComponentActivator>());`
in my `BeinniBlazorModule.ConfigureServices()

but that doesn´t solve it

What should I do here?

• ABP Framework version: v7.0.1
• UI type: Blazor WASM
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

Don´t get your hopes up... there are no errors on my side.. so these gaps will most likely continue on your side .

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…

We managed to figure this out and it was our fault and now everything loads just fine so closing this issue!

So, is this a bug in 6.0.1 and is there a workaround or do we need to wait for next patch?

When logging into Blazor WASM the first time we don´t see the side menus until we do a second F5 refresh of the page Here is a video demonstrating this.

Have you encountered this and do you have a fix for us? This started after updating to 6.0.0

• ABP Framework version: v6.0.1
• UI type: Blazor WASM
• DB provider: EF Core
• Separate (Opendict) Identity Server: yes

Thank you, its Sturla@ibeinni.is