naxhunt.blogg.se

Overall, the update from EF Core 5 / ASP.NET Core was fairly easy. The resulting code can be found in the Part3-Net6 branch, and you can look at all the changes by comparing Part3 branch with Part3-Net6 branch. NOTE: I did NOT plan to change the code to use new NET 6 features, such as ASP.NET Core simplified Program class or EF Core features such as the new SQL Server Temporal Tables support or improved Cosmos DB support. Test the performance of the updated application.Make the 200 ish xUnit tests to run successfully.Convert my book setting web site to NET 6 and get it compile.This means any EF Core breaking changes are likely to been seen on this application. This code is in the Part3 branch and contains 22 projects that use quite of the more intricate parts of EF Core features such as Global Query Filters, user-defined functions, table splitting, transactions and so on. In part 3 of my book, I build a complex ASP.NET Core / EF Core application aimed at testing the performance of EF Core.

Setting the scene – what type of app did I update? I didn’t find any performance improvements, but that’s because my queries were SQL database bound, taking between 10 ms.The EF Core parts, which as complex, had two compile errors on unusual parts of EF Core and a few runtime errors, mainly around the Cosmos DB changes.