I love the style and conversational approach you guys have taken, this is a real pleasure to watch. I've been programming for decades but can watch content like this all day, it's a masterclass in how to explain concepts in such a natural manner. Top stuff!
An amazingly clear explanation that shows how simple LINQ can be at least for beginners like me. I've watched other videos and none of them make a clear distinction between query syntax and method syntax.
Microsoft be like: "How am I going to teach them about data structures without calling it a data structures leason...🤔" Yours teaching method is outstanding!
After years away from writing code in a Windows app, I want to resurrect a 1990s-era Visual Basic desktop app and 'refactor' it in C#. These sessions show me that I can enjoy doing what I did back then in a much more efficient manner. I am also hoping to find sessions that demonstrate how to call Windows functions in the various DLLs that comprise Windows today, and save even more code writing.
This is straightforward in c#. Use System.Runtime.InteropServices. It should be noted that a good portion of the windows API already has .NET bindings, but it’s a good thing to understand nonetheless
I've used C and C++. This LINQ is new to me. But I've also done db queries. Does it matter if from/where/select are in that order? The reason I ask is it would look like a db query if it was select/from/where.
2:16 i have the latest version of visual studio code and the sdk 8.0 but it give me error if i try to List scores = [... it says not available in c#11 plz use 12 or greater, even though i updated sdk to version 8.0 and restart my machine many times, how it is working with u and not working with me, because later it effect the sorting thing int[] scores .... doesnt have sort property. so when u upload lesson just make sure its available in the market, not just for u
create a project like they told in the beginning lectures inside the project folder you can see a .csproj file in it set targetframework to 8 (net8.0) (btw this needs dotnet 8 to be installed to work)
Is the IEnumerable a copy of the list or is it a list of links to the original data? Just wondering from a memory stand point and what happens if there are changes to the original list.
It’s an interface. It just specifies the required method names a data structure implementing that interface need. As a byproduct of that, LINQ will work with any implementation. Your question relates more to the individual data structure implementations
![LINQ Query Expressions From, Where, Orderby, and Select [Pt 16] | C# for Beginners](http://i.ytimg.com/vi/Wy1pvmcEqKw/mqdefault.jpg)
![LINQ Query Expressions From, Where, Orderby, and Select [Pt 16] | C# for Beginners](/img/tr.png)
I love the style and conversational approach you guys have taken, this is a real pleasure to watch. I've been programming for decades but can watch content like this all day, it's a masterclass in how to explain concepts in such a natural manner. Top stuff!
An amazingly clear explanation that shows how simple LINQ can be at least for beginners like me. I've watched other videos and none of them make a clear distinction between query syntax and method syntax.
Microsoft be like:
"How am I going to teach them about data structures without calling it a data structures leason...🤔"
Yours teaching method is outstanding!
This is learning and fun added together. Thanks for the great work.
6:11 "You are not giving a f... formula!" 😂
After years away from writing code in a Windows app, I want to resurrect a 1990s-era Visual Basic desktop app and 'refactor' it in C#. These sessions show me that I can enjoy doing what I did back then in a much more efficient manner. I am also hoping to find sessions that demonstrate how to call Windows functions in the various DLLs that comprise Windows today, and save even more code writing.
This is straightforward in c#. Use System.Runtime.InteropServices. It should be noted that a good portion of the windows API already has .NET bindings, but it’s a good thing to understand nonetheless
I've used C and C++. This LINQ is new to me. But I've also done db queries. Does it matter if from/where/select are in that order? The reason I ask is it would look like a db query if it was select/from/where.
2:16 i have the latest version of visual studio code and the sdk 8.0 but it give me error if i try to List scores = [... it says not available in c#11 plz use 12 or greater, even though i updated sdk to version 8.0 and restart my machine many times, how it is working with u and not working with me, because later it effect the sorting thing int[] scores .... doesnt have sort property. so when u upload lesson just make sure its available in the market, not just for u
Is your project targeting .NET 8 as well?
i dont have project am just following up with ur video step by step, thanks for ur replay@@davidfowl
@@risechess7114 Find solution?
no not yet@@DataScientist268
create a project like they told in the beginning lectures inside the project folder you can see a .csproj file in it set targetframework to 8 (net8.0) (btw this needs dotnet 8 to be installed to work)
Thanks!
Kind of off the subject. What kind of mouse is that?
A kind of ergonomic mouse.
love these guys!
Is the IEnumerable a copy of the list or is it a list of links to the original data? Just wondering from a memory stand point and what happens if there are changes to the original list.
It’s an interface. It just specifies the required method names a data structure implementing that interface need. As a byproduct of that, LINQ will work with any implementation. Your question relates more to the individual data structure implementations
Great video, love it
it does not working List scores = [97, 92, 81, 60]; only work like
List scores = new List { 97, 92, 81, 60 };
no functions
no functions? (ancient megamind meme)
LINQ look like a resource consumer one
Why do they use the word "simpler" to mean "more complicated"?
ah much better way to write lists (and arrays)
Thank you for discouraging the use of var syntax. I disagree with this philosophy. I believe Microsoft should remove this token entirely