.NET 5.0: Preview 8

Microsoft has released .Net 5 preview. The eighth preview version has almost all the main functions, and some of them will refer to the next release candidates and, of .Net 5.0 course, to the major release in November. The provisional date is November 10th.

Chudovo will be happy to share a brief overview of the new functions with you:

.Net 5.0 What’s New?

The open-source framework Blazor will be significantly improved.

Blazor is a free web framework, a product of Microsoft. It provides the ability to create web applications with C # and HTML. With Preview 8, Blazor should send the .NET-5 runtime and libraries. Blazor Web Assembly uses mono libraries. Using the .NET 5 runtime environment brings a lot of productivity gains. According to the .NET team, any CPU code in .NET 5 should be about 30% faster. And the JSON serialization and deserialization increase by 60% accordingly. The Blazor components’ visualization is also significantly optimized.

The open-source framework Blazor will be significantly improved.

What’s new for Entity Framework Core

The ORM mapmaker becomes much better in the first release. It is worth emphasizing the abstraction of N: M intermediate tables. Previously, developers had to model N: M relationships in the object model, as in the database model as two 1: N relationships. The abstraction known from the classic Entity Framework returns that two objects are allowed to have a many-to-many relationship, and the OR mapmaker transparently reflects this to an intermediate table. It makes migrating existing applications from Entity Framework 6.x easier.

.NET software development .NET class can now be the basis for several entity types through Indexer Properties. These general type entities make it possible to compare tables from the database during the application runtime that did not exist at the development time. The previously possible comparison of types to any SQL commands (defining queries) has become better with ToSqlQuery ().

Besides, ExcludeFromMigrations () can exclude the tables from the schema migrations. The OR mapmaker now carries out schema migrations in transactions. Developers can use command line commands to mark pending migrations.

It is also new that the events have been added while launching at the time of maintaining: SavingChanges (), SavedChanges (), and SaveChangesFailed (). Developers can influence the storage process in a SaveChangesInterceptor. The maximum size of commands sent to the database in a batch is now 42. To diagnose, operators of an application can now call up the OR mapmaker’s event counters and Microsoft.EntityFrameworkCore control dotnet counters.