Activities of "roberto.fiocchi@mcsi.it"

We ask that you follow the Microsoft version lifecycle guides https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core#lifecycle

We have software in production created with Abp Commercial and our customers request to use only packages covered by Long Time Support.

If we are forced to migrate to .Net 9 or any STS version we will be forced to look for other frameworks.

Thanks

Because the templates are not yet perfect and sometimes contain errors, I had to customize them. When a new version is released, it is relatively time-consuming to find out whether I can switch back to the original template, whether I have to continue using my modified template or whether I should even perform a merge.

Several possible solutions come to mind:

• Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
  
• Maybe it would also be a solution to store the original file in the same directory with a different file extension (.suite/customized-templates/Frontend.Blazor.Page.Item.razor.original.txt), then you would be able to see very well in Git whether changes have been made in the original (new version) and you would also have the possibility to make a diff with your own changes.
• The "deluxe version" would be if you were to implement a merge tool with which we could update to a new version ;-)

Thanks for the suggestion, I have created an internal issue for this feature request.

I would add that we would need a button like "download Zip with all template"

Thank you, but it is not our practice to perform temporary workarounds when the fix is released soon.

We are waiting for the fix.

Best regards

Will the fix be released in version 8.1-patch or versione 8.2-preview? Which is the estimated release date of the 8.1-patch?

Thanks

Does this fix disable change tracking for all entities? We have AggregateRoot type entities such as Order with List of OrderItem, does this fix have any impact on this? I believe that if I implemented it, I would break other parts of our application.

Can you explain the workaround better?

Thanks

HI, sent you the email with the test projects

When creating an entity with abp suite, in the appservice, use IReadOnlyRepository for lookup entities rather than IRepository so it wont be tracking the entity

I have downloaded Abp suite version 8.1.0 but i still can't create a property of type "DateOnly" and "TimeOnly" inside an entity. When will this feature be available?

Success again today with the release of Abp 8.1.0

I think the problem depends on this https://commercial.abp.io/releases/pr/16597

Thank you, I await your feedback