Activities of "neethucp"

Hi, We don't have access to Azure Application gateway logs, it's in client environment, we are not getting any logs in blazor server application, it's not even reaching blazor server application.

Hi, It just shows site can't be reached after we login and redirect to home page. The cookie size becomes huge as it is now storing the refresh token also. If we revert token refresh flow, the site works as expected. Looks like app gateway is blocking when the cookie size is large.

How is this handled in abp generated projects? Is it better to issue reference token or store the token in cache? We also have the issue of menu items getting cleared when token expires when the application is idle for some time and user returns.

Hi, We tried to refresh the token in blazor server as mentioned here. But this is resulting in cookie size to be huge and is blocked by the app gateway. Is there a better way to handle this?

I really appreciate your swift reply! Is there a scheduled timeline for its release?

But I don't want to update task type when task item is inserted or modified as TaskType is an AggregateRoot. I believe the concurrency stamp and modification time of an aggregate root should not be updated when a related aggregate root changes.

This adjustment would be reasonable if the child entity were an AuditedEntity. For instance, in the case of an Order and Order Items, it might be necessary to update the modification time and concurrency stamp of the Order when an Order Item is inserted or modified. In such scenarios, I would extend OrderItem from AuditedEntity rather than AuditedAggregateRoot.

I believe this is a bug with abp code.

We tried the following code to ignore all entites.

Configure<AbpEntityChangeOptions>(options => { options.IgnoredNavigationEntitySelectors.Add("DisableAllEntity", _ => true); });

Do you think this could have any unintended consequences?

yes, we tested by upgrading to 9.1.1 and ignored TaskType

Hi, we implemented the solution for task type successfully. However, as I previously mentioned, with approximately 20 microservices and hundreds of entities, manually configuring each one and retesting is not feasible at this stage. We urgently need a solution for this, as our deadlines are fast approaching.

Ignoring all entities affected by this issue is not a viable option. For instance, when creating a new version of an entity object, we first load the existing entity from the database, copy its details, and insert the new object into the database. Since the new version might have no direct relationship to the original entity, would this process still trigger an update to the concurrency stamp of the existing entity? We don't want to ignore the entity because we may want to trigger events when navigation properties change for that entity.