Activities of "cellero"

• ABP Framework version: v8.1.1

Using ABP Suite, there are no audit details on the child of a Master-Child entity.

It should follow the same audit level as the base class on the Master.
Do you agree? Any suggestions?

Thank you.

I don't understand your reply. I have already installed 8.1.0.

• ABP Framework version: v8.1.0
• UI Type: Blazor Server

Using ABP 8.1.0:

Running abp update from ABP Suite or CLI the update only attempts to update to version 8.0.5:

Excellent. That has worked for me.

hi zhongfang and cellero

Please share a simple project to reproduce, Thanks.

liming.ma@volosoft.com

I am only encountering this on a large project. I tried to reproduce by downgrading ABP Suite to 8.0.3, creating new project and upgrading to 8.04. But I cannot reproduce by doing this.

Looks to be same issues are this one: https://support.abp.io/QA/Questions/6730/miss-CSS--all-Blazor-pages-are-confused

And creating a new solution using ABP suite 8.0.4 does not have the issue.

I'm getting the same issue.
https://support.abp.io/QA/Questions/6737/Menu-Formatting-lost

• ABP Framework version: v8.0.4
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)

On upgrading to 8.0.4 from 8.0.0 I have lost menu formatting:

The login page is ok The content page seems to be ok.

Help please.

Thanks, but the updates to the collection can be from any client.
I want to set the NotificationChange at the repository level so that a change from 1 client triggers updates to all clients.

Can, for example, the NotificationChange be implemented in the Domain Manager and for that to trigger Observable Collection updates?

• ABP Framework version: v8.0++
• UI type: Blazor
• DB provider: EF Core

I want to refresh data on a Blazor page when data in the collection changes. Do you have any advice / recommendations?

Currently I use a timer but periodically get the exception below - it occurs when one of the clients disconnects.

System.ObjectDisposedException HResult=0x80131622 Message=Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it (or one of its parent scopes) has already been disposed.

I'm considering implementing an INotifyCollectionChanged / Observable Collection: https://blazor.syncfusion.com/documentation/common/data-binding/data-updates But I'm not sure of the correct approach.

Any advice would be appreciated.