DEV Community

Cover image for .NET Conf 2022 in a Nutshell🥜 (Key Highlights to Know)
ByteHide
ByteHide

Posted on • Edited on • Originally published at bytehide.com

.NET Conf 2022 in a Nutshell🥜 (Key Highlights to Know)

If you’re like me and didn’t have the time to follow the .NET Conf 2022 , fear not!

Microsoft has teamed up with various venues across the country to host .NET Conf Live Stream events!

In this article, I am going to give you the summary information (of the most important parts) that you need to know. At the end you will be able to say that if you have seen the .NET Conf (wink wink😉) . Join us as we learn about .NET 7, C# 11, .NET MAUI, Visual Studio and more together!

Before we start the summary by going into the different topics that were discussed at the November 8–10 .NET Conf, let’s quickly look at some highlights that I think .NET developers should know about and be proud of what is being achieved!

.NET Conf Highlights

On the first day of the event they revealed a series of amazing highlights and the first of them has to do with the rapid adoption of .NET 6 versus its predecessor .NET 5 (an incredible +1.8x) with almost 6M active users. Fascinating, isn’t it?

At this very moment it was also revealed that .NET remains the TOP 1 most loved frameworks between 2019 and 2022 (that’s already 4 years!). And little to say about C#, which to this day remains one of the top 5 fastest languages on Github.

Moving on to our .NET developer community (yes, it’s ours! Both you and I are part of this amazing community!), the numbers reveal that almost 50K members have contributed to .NET. 50,000 members! Do you get the idea of what is being achieved? As you can see I am very excited.🥳

Well, now that we’ve done a little review of the important general data of the event, let’s move on to the heavyweights.

📌Full original video source: .NET Conf 2022 Keynote: Welcome to .NET 7 | .NET Conf 2022


.NET 7 Highlights

After the intro made with the higlights, at the .NET Conf they went on to reveal some numbers about .NET 7 and the changes presented compared to previous versions.

First of all we talk about what has been the most talked about in these months about .NET 7, yes, performance.

We start with the incredible figure that more than 1,000 performance improvements have been made in .NET 7:

  • Almost x2 times more than in .NET 6.
  • x4 times more than in .NET 5.

And yes developers, we are in front of the fastest .NET ever seen.

Following the theme of performance in .NET 7, now it was the turn of the APIs, again surprising us all by their high numbers.

At first they showed that the performance improvement of the .NET 7 APIs compared to version 6 is up to 16% faster (reaching up to 25% extra in requests per second in applications such as Fortunes).

But they not only compared it to its previous version. Also the performance of .NET 7 APIs has been compared to its rivals; Node.js and Java Servlet.

As you yourself have just seen, the performance of the APIs is huge (up to 7.02M requests per second) compared to its rivals:

  • 219% faster than Java Servlet (2.20M requests per second)
  • 1070% faster than Node.js (0.60M requests per second)

Another point discussed was the performance of the rest APIs comparing gRPC against its rivals, again, beating them by a considerable margin reaching up to 99.8K requests per second.

Taking these data into account, we can conclude that the performance is:

  • 3.85% faster than Rust
  • 11.63% faster than C++
  • 37.66% faster than Go
  • 44.85% faster than Java (almost half of it!)

It is true that we have been hearing things about minimal APIs for a couple of weeks but I know that maybe some of you don’t know what I’m talking about. Microsoft has been working on super simple APIs to start working on them and with a huge scalability.

As Gaurav Seth, director of PM for .NET_,_ told us in his presentation:

“We are focused on ensuring everyone can build amazing APIs with .NET quiclky and scale to add powerful features as they need them.”

Let’s quickly move on to another heavyweight that has also been talked about a lot these past few months, Blazor in .NET 7.

📌Full original video source: State of ASP.NET Core | .NET Conf 2022


C# 11 Highlights

We came to perhaps one of the most important points of this conference, the eleventh version of the C# programming language.

This time we met Mads Torgersen, C# lead designer, and Dustin Campbell, software architect and C# designer.

In their introduction they told us how the development of C# 11 was structured and organized, and later they began to comment on the different features that this new version brought with it.

If it is true that we have been hearing about these features in recent months, there is not much that we do not know.

In this occasion, apart from the video, I would like to leave the post of Oleg Kyrylchuk, .NET Developer, blogger and Microsoft MVP, and about these C# 11 features.

His explanation is very clear and straight to the point, highly recommended and short reading:

📌Best C# 11 lates features explanation: Explaining New C# 11 Features

📌Full original video source: What’s New in C# 11 | .NET Conf 2022


Blazor in .NET 7 Highlights

This presentation was given by Steven Sanderson, Developer and Architect at Microsoft. He talked about the Roadmap of Blazor releases (which you may already know a bit about how they work).

The most notable thing that Steven commented is that Blazor’s development over the first few months has focused primarily on .NET MAUI:

“…the new Blazor Hybrid feature that allows you to run your Blazor components within a native mobile or desktop application.”

On the other hand, Steven comments that in the last few months development focused on adding new features to Blazor in .NET 7:

As Steven said in his presentation:

“… most of them work across all the different Blazor hosting models so, whether you’re using Blazor Server or WebAssembly or Hybrid with .NET MAUI, most of these features will work in the same way across all of them.”

📌Full original video source: What’s new for Blazor in .NET 7 | .NET Conf 2022


.NET 7 & Azure Highlights

We go into the new features that .NET 7 brings with Azure. For this, Mélony Qin explains that Azure Functions already has support for .NET 7:

“We also made .NET Framework supported in our Functions before host a few weeks back”

At this point you may be wondering what are Azure Functions?

To understand it well, let’s assume a scenario where you are a .NET developer (maybe you already are😎) and to start a project you need to set up dependencies and configurations before you start.

This introduction alone is enough for you to understand what Azure Functions does: it provides you with a ready-to-code environment.

In Microsoft words:

“…Instead of worrying about deploying and maintaining servers, the cloud infrastructure provides all the up-to-date resources needed to keep your applications running.”

📌Full original video source: State of Azure + .NET | .NET Conf 2022


Azure Container Highlights

We come to another interesting topic, the severles containers for microservices. This time we have Anthony Chu, Product manager working on Azure Container Apps:

At the beginning of the presentation, Anthony commented that Azure Container Apps is a new Azure service that came out only half a year ago.

Later, Anthony claimed that Azure Container Apps:

“…allows you to build serverless containers for microservices.”

This is very good news because many developers and development teams are increasingly using containers and development environments.

That is why this new feature of Azure will facilitate the creation of containers in a very simple way so that developers can focus 100% on development.

And this was later affirmed by Anthony:

“…you can focus a lot more on building your app and not have to worry about managing any infrastructure.”

At the time, when I heard that I wondered, what can I really build with Azure Container Apps?

If that’s something you’re wondering right now too, you’re in luck because Anthony has provided a direct answer to that question:

Finally, Anthony discussed application container environments in a little more detail:

“All container apps live in a container apps environment and the environment is basically an isolation boundary.”

In the image you can see graphically how this works. He also added:

“All applications that you deploy to an environment, share the same virtual network and you can also configure them to use the same logging and observability as well.”

📌Full original video source: Azure Container Apps with .NET | .NET Conf 2022


.NET MAUI Highlights

The .NET MAUI presentation was given by Maddy Montaquila, PM at .NET MAUI, and David Ortinau, PM at .NET MAUI, Xamarin and much more (I confess I am David’s fan).

Firstly, they expressed their happiness because the adoption of .NET MAUI has been spectacular: Azure Container Apps with .NET | .NET Conf 2022

The graph shows the number of stars on Github and it is that, at the moment, the difference between dotnet/core and dotnet/maui is barely 1K stars having a difference of about 5 years!

Comparison of repository stars: dotnet/core (left) vs dotnet/maui (right)

Obviously, like all the talk about .NET 7, which is all about performance, .NET MAUI is no slouch with improvements of up to 51% faster rendering.

The comparison table shows this data (tested on a Pixel 5):

  • Xamarin.Forms with 179.38 LOLs/sec
  • .NET 6 MAUI with 327.44 LOLs/sec
  • .NET 7 MAUI with 493.08 LOLs/sec
  • .NET Android with 594.33 LOLs/sec
  • Java with 682.97 LOLs/sec

I’m very sure you’ll be asking me at this point:

What the fvck is the LOLs/sec?

Well then, it has an explanation but before you figure it out, I want to ask you to comment “LOL” if you have really asked yourself that question.

I want to see a lot of LOLs to know how many people have really wondered about this!

The explanation for this… Well, you’d better read this excerpt from .NET 7 Performance Improvements in .NET MAUI:

Yes, they used LOLs on the screen for testing:

LOLs Benchmark (Source: jonathanpeppers/lols)

Did you know this benchmarking technique before? At least I didn’t.

Finally, David showed the roadmap for the release and support for .NET MAUI and one of the things to highlight in this roadmap is that support for the Xamarin SDKs will end in May 2024.

📌Full original video source: State of .NET MAUI | .NET Conf 2022 & What’s new in .NET MAUI and Desktop Apps | .NET Conf 2022

Top comments (12)

Collapse
 
raibtoffoletto profile image
Raí B. Toffoletto

Nice summary ! Tnx. Looking forward to work with those improvements.

But just a note... put a pile of salt in any benchmark made by companies. As I see at work, .NET and Node don't have this disparity in numbers.

Collapse
 
bytehide profile image
ByteHide

Thanks for your time Raí, glad you liked it!

I agree with you regarding the benchmarks, on one hand I understand the companies that want to show (with numbers) what they can do and, on the other hand, I understand the final customers/consumers, that when they test it themselves, maybe they will be upset because of the difference they get with respect to the benchmark shown by the company.

You have commented that in your work Node and .NET do not have that disparity, could you explain what is the scenario/use? The truth is that now you have left me with the curiosity hahaha

cheers :)

Collapse
 
raibtoffoletto profile image
Raí B. Toffoletto

We haven't heavily benchmarked both, but all our projects are basically web apis or websites/webbapps made with nextjs (node as server) or razor pages. Usually they are deployed on 1 shared cpu with one 1gb max of ram... they both handle well lots of concurrent requests and data processing, so I can't see a practical disparity on performance. However both tecnologies scale up very differently, so to handle that amount showed in the charts strategies are different. (Throw more cores and ram do nothing to node if you don't spawn multiple instances and use a load balancer for example) So I wonder how they got the numbers. That's all! 🙂

disclaimer: And although personally I'm very critical to Microsoft practices most of the time I do like a lot dotNet to build web apis!! I had to port projects using dotnet core 2.2 to 6. and I think it didn't take me even a full hour.

Collapse
 
iamjaydev profile image
iamjaydev

👏🏻👏🏻👏🏻

Collapse
 
enry20k profile image
enry20K

LOL

Collapse
 
jwp profile image
John Peters

Excellent tx.

Collapse
 
lidiaaadotnet profile image
lidiaaadotnet

I'm already waiting for .NET 8 and C# 12 LOL😎

Collapse
 
bytehide profile image
ByteHide

Why do you always live in the future?👽

Collapse
 
vballester profile image
vballester

Very good summary! I didn't know about the LOLs hahaha

Collapse
 
pramon18 profile image
pramon18

LOL

Collapse
 
daveslatin profile image
Dave Slatin

LOL

Collapse
 
aymanalhaik profile image
Ayman Alhaik Sy

LOL, Nice Article thank you