Activities of "roberto.fiocchi"

this topic is only for feature requests. we don't iterate a conversation here to keep this list clean and neat. could you please ask your request via email or within another question.

Hi Alper, this is a feature request, see my post https://abp.io/qa/questions/3052/3a112b63-44ce-975c-4a5d-4e1eebde98cd (11 months ago) I also already sent an email to info@volosoft.com

Feature Request: Implement the real-time notification system

This feature request was marked on your roadmap more than a year ago.

Thanks

11 months ago
https://abp.io/qa/questions/3052/3a112b63-44ce-975c-4a5d-4e1eebde98cd

Using Blazor Wasm:
Implement the real-time notification system already present in AspNetZero

P.S: We are having difficulties moving from AspNetZero to Abp framework with all of these features missing

---

When will this feature be implemented?
https://docs.aspnetzero.com/aspnet-core-mvc/latest/Features-Mvc-Core-Notifications

It has been on the roadmap (https://abp.io/docs/latest/release-info/road-map#application-modules-ui-themes) for months and for us it has become important and urgent.

We waited thinking it was in development, but we've had no feedback on whether it actually was or not and when it would be ready.
We won't make another custom implementation to be thrown away.

Can you provide me with some information about it?

Thanks

Hi @Alper, do you have any news about this?

I also received the news of the end of support for AspNetBoilerPlate https://aspnetboilerplate.com/endofsupport

We would like to migrate our project from AspNetZero to Abp.Commercial, but the lack of this service (https://aspnetboilerplate.com/Pages/Documents/Notification-System#user-notification-manager) is a problem for us because the solution is monolithic and we do not want to migrate to microservices or use Distributed Event Bus logics

Can you tell me if the service is planned to be ported since it is always indicated in the roadmap?

Thanks, Roberto

Can someone from Volosoft answer my question or do I need to open a separate ticket?

Thanks

I ask you to update the documentation by adding this clarification and an example how to avoid the problem.

Thanks

As for your problem, I honestly can't find any other method. This is how Blazor Web App works and there is nothing to do about it. If you want it to render completely on the client side, you can use the Blazor Web Assembly template directly, but the first render time can take a long time. I know this situation is very annoying, but as I said, the problem is not caused by us, Blazor Web App works like this in itself

Could Volosoft check if better loading is possible? https://learn.microsoft.com/en-us/aspnet/core/blazor/webassembly-lazy-load-assemblies

https://www.telerik.com/blogs/blazor-basics-lazy-load-assemblies-boost-performance-blazor-webassembly

Hi,

Thanks for the reply, i understand now what the issue is. I have a few questions reguarding this approach. Why would leptonX render both toolbars regardless of if im viewing the page from mobile or desktop? Wouldn't it be better perfomance wise if they only rendered when necessary? Is there an option to achieve this rather then having them both render always?

Hi,

The problem and solution you describe are not actually what is causing this problem because prerender is already set to "false" in the base ABP framework Blazor WASM project:

It seems the problem is specifically the toolbar because if i make a copy of the "Notification" component and add it to a page, the "OnInitializedAsync" function only runs once.

This is what happens when the component is in the Toolbar:

This is what happens when the component is in the Page:

Hope this clarifies the problem i'm facing.

Hi,

I modified the component in the guide to log "Notification component initialized!" when the componenent initalizes. The code is the following:

@using Microsoft.Extensions.Logging
@inherits Volo.Abp.AspNetCore.Components.AbpComponentBase
<div style="color: white; margin: 8px;">
    <i class="far fa-bell" @onclick="ShowNotifications"></i>
</div>
@code {
    private async Task ShowNotifications()
    {
        await Message.Info("TODO: Show notifications");
    }

    protected override Task OnInitializedAsync()
    {
        Logger.LogInformation("Notification component initialized!");

        return base.OnInitializedAsync();
    }
}

As you can see in the following screenshot when i load in the application it prints the Log 2 times:

Same thing is noticed if you put a breakpoint onto the "Logger.LogInformation" line, it runs 2 times.

How can we fix this?

11 months ago https://abp.io/qa/questions/3052/3a112b63-44ce-975c-4a5d-4e1eebde98cd

Using Blazor Wasm:
Implement the real-time notification system already present in AspNetZero

P.S: We are having difficulties moving from AspNetZero to Abp framework with all of these features missing

---

When will this feature be implemented? https://docs.aspnetzero.com/aspnet-core-mvc/latest/Features-Mvc-Core-Notifications

It has been on the roadmap (https://abp.io/docs/latest/release-info/road-map#application-modules-ui-themes) for months and for us it has become important and urgent.

We waited thinking it was in development, but we've had no feedback on whether it actually was or not and when it would be ready. We won't make another custom implementation to be thrown away.

Can you provide me with some information about it?

Thanks

Hi @Alper, do you have any news about this?

I also received the news of the end of support for AspNetBoilerPlate https://aspnetboilerplate.com/endofsupport

We would like to migrate our project from AspNetZero to Abp.Commercial, but the lack of this service (https://aspnetboilerplate.com/Pages/Documents/Notification-System#user-notification-manager) is a problem for us because the solution is monolithic and we do not want to migrate to microservices or use Distributed Event Bus logics

Can you tell me if the service is planned to be ported since it is always indicated in the roadmap?

Thanks, Roberto

• ABP Framework version: v8.3.2
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Steps to reproduce the issue:

1. Creating an ABP solution (v.8.3.2 Blazor WASM)
2. Follow the guide: https://abp.io/docs/latest/framework/ui/blazor/toolbars#example-add-a-notification-icon to create a component and add it to the toolbar.

Dear Support Team,

I am working on an ABP project using version 8.3.2 with a Blazor WASM frontend. I followed your guide to customize the toolbar and add my own component Specifically, I created a class implementing IToolbarContributor, added my component to toolbar.Items, and configured the toolbar in BlazorClientModule.

However, I have noticed that the initialization of the component inside the toolbar is executed twice.

Could you help me understand why this is happening? Is this a bug?

The double initialization is problematic for me because, during initialization, I need to make server calls, register events, and attach to a SignalR hub, among other things. The duplicate initialization is causing unexpected issues.

Thank you for your support.

Best regards, Roberto

Hi,

        PreConfigure<OpenIddictServerBuilder>(serverBuilder =>
        {
            serverBuilder.SetLogoutEndpointUris("<your-blazor-root-url>");
        });

Seems to change the "Logout Url" (the url you go to when logging out) rather then "Post Logout Url" (the url you go to after having logged out).