Can't keep up with these c# versions, 10, 11, 12, 13 ....♾

I would love to see linux support for MAUI, make it truly cross platform

try - catch, definitely. I write tons of I/O stuff and exceptions don't always happen when you think they will. For example, you can test a file to see if it has locks (or whatever), then believe that everything will be okay when you start reading it (big file), half-way in the read, a network card crashes (or drive hiccups, or what-have-you), then your IF check is worthless, and your program crashes because you didn't use exception handling. Believe me, stability is FAR more important than SPEED. A slow program is a nuisance, but a crashing program can be a career changer!

Enum extensions are going to be insane

The only time I had to use list of objects was for integrating with a crappy api (for a specific accounting program).

Would be cool if they could add a ‘when (Age >= 18)’ and allow an ‘if (person is Adult adult) …’ pattern. 😊

Sort of looks like Ruby mixins.

weird way of creating interfaces and using inheritance

Implicit extension makes sense, but explicit extension doesn't. It's inheritance. If it allows to "extend" sealed classes, then it ruins the concept of sealed classes.

Seriously more way complicated. Thanks for the video.

Yeees!!

It is very great that they finally did something with that! However, my main struggle, and the main reason why I rarely use extension methods, is because it is impossible to mock it during testing. With this new way of doing thing, will we be able to mock this for testing purposes?

I've been waiting for this forever! Next question.... in these extension "classes", can you also define extension operators??

How can i see the Viewer for the low level code? Thanks

Awesome Video!! Keep pumping them out :)

So basically improved inheritance?? Can inherit classes and extend properties currently. Not sure exactly what has changed other than syntax.

Hopefully 14 comes with DUs. It would be good to get it in LTS version

Wait a minute... the explicit version is basically inheritance. You could just create a class called Adult that inherits from Person and do exactly the same thing. Would be nice to see a genuine example of where explicit becomes useful and something new.

You explained it so clearly! 🤩 It'd be awesome if you continued this as a series with more concepts.

How do you secure the dashboard. I mean if you run this in a production environment, can you add access rights to it? And can you also see to it that some environment variables are masked, as in some situations there is one team handling the system and another team handling the development and they aint usually allowed to access passwords but they are interested in seeing logs.

Can someone explain why the explicit extension isn’t just the same as inheritance ?

To whom having issues with the generated token, please ensure of the order of app useauth and use authorization. That was my point. Here is the order : app.UseAuthentication() .UseAuthorization();

I have no idea why started this NSwag is better maintained thing goin, but it is just stupid. It tooks them months to add .net 8 support after .net8 release. NSwag litterellay has 1700 open issues and 100 PRs noone ever looked at.

I found this feature by accident. I had to write some empty classes and structs to use with code generators, and I wrote them as I would in Rust, with just the semicolon after the name. A few minutes later when it successfully compiled I thought to myself "Wait, that shouldn't have worked"

This is pretty great. Discriminated unions is THE feature to fix exception nonsense in enterprise code or OneOf nonsense in smaller personal projects.

What is the difference between explicit extensions and class inheritance?

#4 as Scope boundaries are more visible and explicit with curly brackets

So, what's the difference between explicit extension and inheritance?

100% agree "implicit" extension is a game changer. However, how is "explicit" extension different from regular inheritence (i.e. "public Person : Adult")?

Imagine what cool things that eventually enables with source generators

I like it, but I can't imagine use-case for the explicit extension. I always thought that the extensions classes are being used to extend existing types that I cannot control well (so I think the implicit extension is absolutely awesome), but the explicit one feels to me like it creates a new type derived from the type you are trying to extend. Now I wonder if it's a really new type (so it will shown differently in Reflection, etc) or if it is still the same old type, just with some kind of an alias or something.

will we be able to use pattern matching "if(person is Adult adult)"? And is it possible to add operator behaviour to any type? I often want to add the values in a vector but there is no built in + in vector, and you cant do it yourself directly on the System.Numerics.Vector class so far

I wonder how many discussions this is going to give about extensions vs inheritance. And also what this means for serialization as mentioned in another comment.

I feel like the explicit extension is just plain old inheritance. What am I missing here?

So this means the explicit extension is just the same as a subclass?

I hate extensions.

What is the point of the explicit extension when you could just inherit from a class? Or am I missing something? Are they just trying to make C# syntax prettier?

This is the content I've been waiting for. How would you handle versioning of events and views - adding and removing properties, etc.?

"or maybe another time..." proceeds to silently write 0.69

Great stuff, Do you happen to test/check how this implicit/explicit extension properties will behave when serializing/deserializing to a Json for example?

Feature looks great if you use it with some consideration. It can also be abused in new unexpected ways by devs that think they're smart, when they aren't 🙂

I've been waiting for this feature for years. This and DUs, but I think I need this one more.

I can already say I am going to use this all the time. I would like it if they made it slightly more like Rust's trait impls than it already is, and let you implement interfaces as an extension.

Why using "@" when defining Event @event as a param. Is it a convention ?

I wonder how the explicit extension works under the hood.... It would seem as it would allocate a new region in memory. How this is done is important for game dev for example because if the memory region of the extended type is scattered, it can cause a bunch of cache misses.

Beautiful and what sealed class?

I didn't go through all the comments on the GitHub proposal, but does anyone know if conditional extensions have been discussed? I was thinking that a condition on the extension could make type-checking a lot more powerful, for instance, like this: public explicit extension Adult for Person person when (person.Age >= 18) { public string FavoriteDrink => "Old Fashioned" } That could potentially allow me to write this: if (person is Adult adult) { var favoriteDrink = adult.FavoriteDrink; }

Do c# extension have something like the orphan rule? Looks like explicit extension is a better way than orphan rule, but i'm still curious about whether implicit extension requires this rule.

Isn't this thing (extension) already around since some previous versions? Maybe since c# 8 or 9?

That's a dumb shit