What's new in .NET 9 and C# 13

[@jfversluis]

Amazing stuff Filip! Thanks for the update!

[@FilipEkberg]

Thank you Gerald!

[@rahulsingii]

Thankfully YT suggested your video. Thank you for the great video Filip, crisp as always :) All the best for your channel!

[@sathishd273]

Very useful information. Thank you🎉

[@OThyme]

Really a good wrap up - MS could learn a lot from you - make some more videos

[@19balazs86]

Thank you, Filip, for the excellent content on the new features. Your video is invaluable 🙏

[@FilipEkberg]

Thank you very much!

[@thatnod]

Thank you Filip, I can skip .NET Conf now! 😂

[@Dron0031]

Yeah.. that's lengthy

[@emillarson89]

Fantastic walkthrough!

[@yuriitsurul3850]

Thanks for great intro! Keep up the good work!💪

[@99aabbccddeeff]

Great video. Thanks for this overview!

[@RobUttley]

Thank you Filip.I would certainly be interested in your summary of what has been added or changed from a Maui perspective.

[@tabareh]

Thanks! Noticed a slight difference in results in the base64url demo. Here is the clarification from Chat GPT: The difference in results between `Base64Url.EncodeToString(data)` and `Convert.ToBase64String(data)` in your code is because they use two different Base64 encoding schemes: 1. **Base64Url Encoding**: `Base64Url` is a URL-safe version of Base64. It replaces the `+` and `/` characters with `-` and `_`, respectively, to make it safe for URLs and filenames. It may also omit padding (`=` characters at the end), making the encoded output slightly shorter. 2. **Standard Base64 Encoding**: `Convert.ToBase64String` follows the standard Base64 encoding rules, which include `+`, `/`, and padding (`=`) to make the encoded string compliant with the Base64 specification. In short, the output differences you see are due to these substitutions and padding rules in URL-safe Base64 encoding.

[@FilipEkberg]

Yep! That’s the whole point of the example to show the difference. As the old approach many had wasn’t actually URL safe at all.

[@tore28]

I added a short article about this here : toreaurstad.blogspot.com/2024/11/url-encoding-base-64-strings-in-net-9.html

[@yassinebouchoucha]

as Fullstack Js/Ts developper I see a lot of contents around c# and the .NET ecosystem ! what made this shift? even this channel ! keep up with updated implementations 🔭

[@FilipEkberg]

That’s a great question! I think it’s more popular than ever, especially since it’s viable for full stack development. The rather fast cadence of updates also means there is going to be a lot more buzz!

[@9739718777]

Dotnet & C# has the tone of exciting new stuff. That's exactly a problem for developers. Feature additon is faster than its adaptation😮

[@WailGree]

Just found your channel. Amazing explanations. Subbed and let the bell ring!

[@FilipEkberg]

Awesome, thank you!

[@superpcstation]

Thank you Filip!

[@sean109]

Welcome back, Filip!

[@FilipEkberg]

Thank you Sean!

[@superpcstation]

Please consider making an Aspire getting started video

[@kirillnovikov8269]

Great video, thank you!

[@pkmx-um9vb]

Thank you, great content 10/10 👍, and presentation 10/10 ...

[@FilipEkberg]

@@pkmx-um9vb Thank you for the kind words!

[@ericaY-l4x]

Thank you

[@alexclark6777]

Skip to @19:21 for the addition of discriminated unions.

[@FilipEkberg]

@@alexclark6777 hah 😂

[@ozanyasindogan]

thanks, great video

[@m3coo]

thanks!

[@MrLucki001]

AFAIK field keyword is not included in the official version of C# 13. They removed it for the current version.

[@FilipEkberg]

Looks like they moved it to ”preview” last minute. It’s still available and shipped with .NET 9.0 but you have to set the LangVersion to preview. It’s because it’s a pretty breaking change.

[@olivier0003]

Great and unvaluable

[@WalkorBikeinCities]

👍👍👍👍👍👍

[@user-wc3tz3be1j]

it's changing a little too fast 😁 hope older features still stay the same in the future. They might even mess with them who knows

[@FilipEkberg]

I think they will avoid breaking changes as much as possible!

[@SajadJalilian]

After 4 years you dropped something with this quality? I think you should take your channel more seriously. Cheers

[@FilipEkberg]

Thank you for the very kind words and encouragement 🙏

[@Athurito]

thought type results are delayed?

[@FilipEkberg]

It’s available: learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.typedresults?view=aspnetcore-8.0

[@siriusjaeger2823]

No sortable Guid? :(

[@FilipEkberg]

They’ve added UUID v7 in .NET 9.0. Is that what you are looking for? learn.microsoft.com/en-us/dotnet/api/system.guid.createversion7?view=net-9.0#system-guid-createversion7

[@citizendc9]

"Hopefully everyone us using nullable reference types". Why would everyone want to use this feature?

[@FilipEkberg]

That's a great question! It was introduce in C# 8 and I have a separate video on the subject. In short, it changes how the compiler looks at all your reference types (classes, strings, objects). Instead of assuming that they are null, which they are by default, the compiler will do it's best to tell you if you have forgotten to set it to a value. This means that you can avoid null reference exceptions. To allow an object to be null, you would decorate it with a "?". or example: string? optionalName = null; While this would give you a warning because it should not be null: string name = null; Hope this helps!