Activities of "roberto.fiocchi@mcsi.it"

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

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

1. Create a solution with Abp 8.1.0.rc.4
2. Add Entity “Book” with Id int, Code String 10 Required , Title String 100 Required
3. Open BookManager.cs add the following code in CreateAsync (only for test)

#region test InsertMany
var myBooks = new List< Book >();
for (var i = 0; i < 12000; i++)
{
	myBooks.Add(new Book(i.ToString(),$"Title-{i}"));
}
    
Stopwatch stopWatch = new Stopwatch();
stopWatch.Start();

await _bookRepository.InsertManyAsync(myBooks, true);

stopWatch.Stop();
TimeSpan ts = stopWatch.Elapsed;
Console.WriteLine(ts); 
#endregion

4. Lunch in Debug
5. Via Swagger Post a new Book
6. Track the time from console log o via breakpoint. On my Pc is 00:00:05.7310325
7. After that upgrade to Abp 8.1.0
8. Lunch in Debug
9. Via Swagger Post a new Book
10. Track the time from console log o via breakpoint. On my Pc is 00:05:05.4026061

It takes 60 times longer !!!

We use InsertMany in import jobs and execution times have now gone from a few seconds to many minutes and those that used to take a few minutes now take hours.

We cannot upgrade to 8.1.0 stable because it would block the application in production.

From the release logs there is no evidence of changes in this area.

What has changed?

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