Видео

thank you for video, clear explaination.

This is exactly what I was looking for. It's surprisingly hard to find good information on structs because people always just say not to use them and start talking about premature optimization. However, sometimes performance is important and if you understand why and when to use them there's nothing premature about it; it's simply optimization.

The advise on using Task ctor is flawed. There are many scenarios to create not started tasks.... If you don't have any specific requirements to create a task, you don't need to use factory, just use the Task ctor.

vscode and vs2022 and vs2019 it is really not that hard.

Its because 7 eight 9

I really dislike the visual studio and vistual studio code naming, it makes it really annoying to search

C# is just 1 languege in .NET ecosystem with other 20 langueges sharing same features and libraries. all those langueges are compiled to MSIL (bytecode) which can be launched as JIT ("just in time" like Java) or AOT ("ahead of time" like C++) you can have 1 program with parts writen in different langueges .NET framework is old framework with lot of bloat from old versions (backward compatible) and work only on windows .NET Core is crossplatform written from cratch

Cool

C# is not .NET, it's a part of .NET like Java the language is part of the JVM ecosystem

0:47 its because of it that before windows 10 would be the last windows operating system, so they used 10 cuz its round and complete when 9 it suggesting that will be another windows os.

On Visual Studio note, there's a third one. It's called Blend for Visual Studio.

They unified blazor server and wasm with .NET 8, so this is a single product now

They likely skipped 9 because a lot of existing code looked for 9 to detetmine if os was 9x (i.e. 95, or 98).

java > c#

Microsoft is not the only one guilty of that, Google and Apple also come to mind, out of all tech companies, probably, only Sony is consistent in their naming practices. With them you know that the bigger the number, the newer the model. Even Sony Ericsson followed that practice. They fumbled it a little with their headphones though, like what in the world is WH-CH720N

Good examples of MS namings: Microsoft Message Queue (compare to Kafka). Notepad (compare to gazzilions of nonsense). Internet Information Service (compare to Apache httpd). Internet Explorer is the perfect nane (RIP)

“Visual Studio, the blue one” and “Visual Studio, the purple one” is how I explain it to people 😂

Because Microsoft sucks

...And here I was annoyed about the _all Pascal-case_ naming. LOL.

Another thing is the C# convention of prefixing interface names with “I”. I feel like it’s very redundant and unnecessary. In my opinion, Go is a perfect example of interfaces done right. They typically contain a single function and the interface names end in -“er” (e.g. Logger, Reader, Writer, etc).

So... is .NET just C#? Or is it a superset of C#? Or is it a framework on top of C#? Is C# automatically .NET? I'm confused

Ngl I never had problem googling VS and VScode because most of the time, seemingly no one has the same problem and the search result is completely irrelevant.

microsoft be microsofting

they skipped 9 to avoid confusion, a lot of old programs refer to win 95 & 98 as windows 9.

the best example i've seen is the .NET bindings to the macOS libraries. (formerly called Xamarin.Mac) The framework version is net8.0-macos, the library you reference is Microsoft.MacOS, the docs call it ".NET for macOS" (or if you're unlucky, just .NET) The GitHub repo is still called xamarin/xamarin-macios even though Xamarin is dead. Good luck googling for any of that and getting relevant results

I didn't even know. .net is the new name for..net core. That's going to get people who are just starting out in a bit of hot water when they follow an old.net solution.

stealing terms for their own use, windows, dos, C, net, surface, the number one.

C# and dotnet is different though??? It's like comparing java with jvm. Kotlin exists. So do f# and vb

"DotNet" and "CSharp" work in Google.

Let's not forget that Razor Component files are named .cshtml and Blazor component files are named .razor /)_-

>using dotnot found the core issue

Wow! Great comments feel the same can be said about car models 😂

Not to mention that Windows Powershell is different from Powershell.

i love this video

Windows 9 was skipped to avoid bugs with versioning in spme older tools, which effectively only look for first character in version string.

Adding to the blazer part: and it is done in .razor files, which doesn’t have basically anything to do with the thing called razor xd

jeez, how on earth could Windows Forms, Windows Presentation Foundation, Universal Windows Platform, WinUI 2, WinUI 3, MAUI, Windows App SDK, or any of the other UI framework names ever confuse anyone??? /s

most naming shenanigans happen for historic reasons, everybody thinks the previous guy got it wrong, and a couple decades later it's a mess

.net is not just c#, there are also f#, powershell, visual basic and some third party ones

microsoft people coming up with codenames: cools stuff like chicago, longhorn, scarlet microsoft people coming up with actual names:

Microsoft doesn't know how to name variable 😭🙏

Very good video, it is the in depth explanation I was looking for, thanks!

in the Eliding examples you show the eliding method in the first example only executes at the await which is where you would need to put the try catch. Then in the next example the eliding method executes and throws the exception before it ever hits await. So what is the difference between the two. I wish you would have left the GetSomethingInternalAsync methods the same so we would be comparing apples to apples but as it is, it is confusing. Is Task.FromResult making the difference? Because in the second example all you say when discussing that line is "it will perform anything after the the first await here as well" which makes no sense because no await has been called yet unless you are talking about the await from the previous GetSomethingAsync method called earlier.

Good introduction. I also liked the use of IServiceScopeFactory<T>. Slightly more slick than my usual approach. 💪

Regarding Asyn suffix. Its advisable to add this suffix 1) when you have synchorios version of the same method in the same class 2) if this method is async void then IDE might not help 3) just to increase readability.

Thank you for the great explanations.

Fine case yet so far. But about that DI container. We can actually register an interface multiple times without overwriting. Just give it an alias and bam you're done.

Thanks so much for this clarification

Excellent explanation, thank you so much

Great video on a difficult topic. Thanks!