Every single feature of C# in 10 minutes
HTML-код
- Опубликовано: 11 мар 2023
- Get ready to become a C# expert in just 10 minutes! In this video we'll cover every single feature of C#, from the basics to the advanced. If you already know another programming language then this crash course will give you all you need to know to transfer your skills.
#csharp #dotnet #learncsharp #csharptutorial #csharpbasics
📖 Get my book - Developing on AWS with C#
www.oreilly.com/library/view/...
🔗 More guides & articles
traintocode.com
💻 Github
github.com/traintocode
🗣️ Social Media
- / jamesjcharlesworth
- / jcharlesworthuk 
Наука
I have used C# for roughly 5 years now, and I still learned something new!
Thanks! It is a very feature-rich language, more than most
Never too late to learn the "if" statement
I've been using it for years too, I had no idea of the newer stuff they added such as the functional switch statement, that's cool!
Love this, great job. I'm an experienced programmer in other languages (C, C++, Java, etc.) and this is just the right level for me - not too little, not too much, perfect pace. It's great to have a quick survey, and when I need more detail I'd rather drill down into a written manual anyway than watch a video. Thanks!
I've been programming in C# since 2006, and this video had a few things I had forgotten. Thanks.
that record type, wtf, also the deconstructor, never used one lol
I'm learning C# as another language after Python and this video was exactly what I was looking for, thanks
I've been working with C# for 1 year and the experience has been very smooth. Also, great video!
6:55 It´s important to mention that the using keyword in C# does NOT include the entire System.Collection.Generic but just makes it easier to type collection type in that file. Like instead of having to write System.Collection.Generic.Dictionary myDictionary = new System.Collection.Generic.Dictionary(); we can ommit System.Collection and just write Dictionary myDictionary = new Dictionary(); instead.
That is a good point thanks
@@traintocodeyeah using System; ≠ using system.Drawing;
Actually a very good presentation. Pls do it in the same manner on different languages
This is definitely one of the most concise, loaded with information video I’ve encountered so far about C#!!
Thank you for making this amazing video!
thanks!
very nice, I have been using C# for 15 years, read books, watched other videos etc. yet this is really useful and educational in just a short video. Thank you !
Brilliant. Thank you for this.
No worries!
Very informative. Thanks!
The best ten minutes of education I've had in a while.
wow thanks that means so much!!
Very useful, thanks! Exactly what I was looking for.
이 영상으로 ^o^ 인해 새로운 동기부여를 얻었습니다.
Huge thanks ❤
It's the kind of video, that should be made for all other languages. Perfect set of features and timing! Thank you!
Thanks will do soon
better than many courses
🎉🎉🎉
Fantastic!
Awesome man you taught alot to me in 5 mins coz i saw it in x2 speed ... KEEP IT UP MAN
I talk dead fast if you put me in 2x speed that would be impressive
Congrats you're almost at 1k subs🎉
Thanks! I just hit that 🎉 what a milestone thanks so much for your support!
@@traintocode Congrats 🎉
I think i have c# brainrot, i love c# i like it alot its the perfect mix between usefull and simple, the language syntax just makes sense yet you can still do performant things when usings spans and things alike
I'm just starting to learn C# and wow....I have a lot to learn.
this is gold
이 'ㅂ' 영상을 기다리고 있었습니다!
Love the video, if you can have another one 10-15 minutes with Events, delegates , or API just simple as this fast and to the point.
I will do a follow up at some point there is LOADS I didn't cover. C# is a huge language.
I love C#. Keep them coming, just subscribed.
Thanks!
I played this video at 2x speed and now I'm an expert in 5 minutes.
Careful now.
I enjoyed this ;)
thanks!
@traintocode you are like brackeys' successor
Simply Beautiful
Thank you! 😊
What if you have a mutable type in a record, like an array? I assume you can change that?
Asking as a functional programmer.
Interesting about the => notation. Is there no final / const keyword? Is that to take the place of final / const?
That's rather unusual that instead of returning a tuple of values, the deconstructor actually includes the values in the parameters.
How does that work if you don't care about one of the values?
I find the PascalCase / CamelCase a bit off-putting, as I do the C-style convention of putting the opening brace on its own line... it just takes up so many more lines of code than putting it on the line where the class / method / etc. is declared.
Can methods be declared with a var return type to have auto type deduction?
How in-depth is the pattern-matching? Again, as a primarily functional programmer, some languages have really amazing pattern matching abilities.
Don't worry about answering these... it's just me thinking out loud.
This was an awesome video. I just got the Functional Programming in C# 2nd ed book from Manning to jump in feet first, but having never really used C# before (although knowing Java, Kotlin, and Scala well), this has been a really handy introduction to cover the basics that may well get me up to speed to the point where I can read the book without needing to go through a beginner text. And yes to Rider! I love me some JetBrains and buy the yearly subscription. CLion is the only C++ IDE that I can not only tolerate, but actually enjoy using.
🌷💐🥀 شكرا جزيلا🌻🌼💐
Maybe I’m the only one here but I hate implicit typing with a passion. Why would I ever want to put a barrier up for knowing what type I’m dealing with?
It feels to me that except in a few situations where you could get different types being returned to you and this gives you an option for how to handle that, that I’m always better off making the effort to be explicit in my use of types as it’s far clearer to read?
Beautiful brief.
it should be remaked whenever new version released!
Not sure I understand SquareEach. Shouldn't it be "yield squared"?
Do we have an Enum with a wrap value in C#? (I like the one we have in Swift)
enums in C# are just a group of constants, usually integers. Color.Red=1, Green=2, Blue=3 etc. They don't wrap values like enums in some other languages like Rust. You can do that, just not with enums.
C# is a bit confusing for me because I've worked with C++ but never worked with OOP much, other than simple game scripting in C++
This video just gives a very quick overview of some of the functions of C#, but not all... THanks, but it was tough to follow for me.
Pls do mire videos on c# vs code am stuck with it🤔
Goddam, I thought C# was going to be this whole thing, like learning to speak Spanish. But a year later I realise the actual vocabulary and rules could fit on a single note page.
Wrapping your head around them and practising is the hard part.
Great simple and straight forward without wasting time +1 but you missed Delegates, Reflection and Extension methods.
Great point about delegates and extension methods I definitely missed those. Reflection I'd say is more a feature of .NET and not specifically part of the C# language spec. There might be uses of C# that don't support reflection. Maybe I'll do another video on features of .NET which can include all sort of things in the System namespace!
한국 ㅠㅠ 인 어디 없나요?! 자랑하고 싶은 마음이 몇 배가 됩니다~~
When I saw the title I already knew that it would not fulfill it's promise :D. Almost at every point I had something to complain. Though sometimes I might be a bit picky.
00:36 "Each line is ended with a semicolon". Well especially for new users of the language this can be misleading. Not every line has a semicolon at the end but every statement. It's a bit difficult to explain this in easy terms, though it's certainly not every line. Common beginner mistakes is putting a semicolon at the end of an if statement which would end the statement right there. So the following body has no connection to the if statement this way.
00:46 Besides line comments, there are multi-line comments using /* This is a comment */
01:26 Just like to point out that the primitive type list is a bit longer than what was shown here ^^
01:39 Well, he said DATA-types so we might forgive missing enums, delegates, interfaces and closures.
02:01 This is a common misconception. Structs don't live on the stack unless their variable is declared on the stack. Structs are value type and as such are directly stored in the memory of the variable itself. So it depends on where the variable is stored. When the variable is a field of a class, that struct would live on the heap.
03:00 This is just false. A private class can of course have a public field or method. How would you interact with anything in that class? When a nested class is declared private, it can only be used inside that class and can never be exposed to the outside. So you can not declare a public or ptotected field of your private class type since from the outside or a derived class, that nested class would not be visible. However the fields and method inside the private class can have the full spectrum of modifiers
05:20 Those unfamiliar with C# probably should know about logical and, or, xor and not operators which are &&, ||, ^ and ! respectively. Personally I get some itching when tutorials show boolean variables inside an if statement compared to true. An if statement simply requires a boolean value. Those logical operators will return / produce a boolean expression. However a comparison with true is completely unnecessary. You could also do if (aBoolVar == true == true == true) which does the same as if (aBoolVar). The comparison of boolean operators don't need to be used inside an if statement. You can also use them to assign a boolean value. bool myVar = someString == "Hello" && age > 18;
05:57 This is called a "switch expression" which actually evaluates to a value. A switch statement is actually a control flow statement which does not evaluate to anything, like an if statement or for loop.
06:49 Even though I don't like them because they have a lot of overhead, it should be mentioned that you can have multidimensional arrays as well. They may look useful, but the performance isn't that great. For every access it has to do a bounds check on each dimension / index and calculates the flattened index every time. In most cases, especially in time critical situations (when you create games and not business apps) just using a normal 1d array and calculating the index yourself can be way faster as you usually would use nested for loops and you can pre calculate some of the offsets in the outer loops. Also when it's a 1d array it's much easier to iterate over all elements regardless their spatial relationship.
06:55 Small mistake here. The System.Collections namespace does only contain the untyped / object variants of those collections. All the types shown there are inside the System.Collections.Generic namespace. You almost never want to use the untyped variants. They are essentially an ancient leftover. Even when you want to store System.Objects / objects, most people would still use the generic List with the type object rather than the ArrayList.
06:58 It should be pointed out that "importing" a namespace does not load anything like in other languages where some kind of import would actually load or embed another file. Such a using directive will "just" shorten the type names. So this is a pure organisational feature. We use namespaces to avoid name collisions. Different namespaces can have the same class / type names, but you can not "import" both as when you get a name collision, the compiler would complain as it can't tell which type you wanted to use. It's possible to "import" or resolve individual types by: using MyType = Some.NameSpace.MyType; Here we can even rename / give the type a file wide alias name
07.23 This is only partly true as the foreach loop does first and foremost use pattern matching and only resort to the IEnumerable interface when no pattern could be found. The pattern the compiler looks for is simply if the instance passed into the foreach has a method GetEnumerator and if the returned type has a MoveNext method that has no arguments and returns a bool, and it should have a Current property that is readable. If those conditions are met, the compiler will just use those methods, even without the interface. Most of the built-in collection types use struct enumerables / enumerators to avoid creating garbage on the heap.
07:34 Again, the generic version of the IEnumerable is in the System.Collections.Generic namespace. The untyped / object version is in the System.Collections namespace.
08:44 Just to use the right terminology, the stuff after the "where" keyword is called constraints. Several constraints can be specified by separating them with a comma. Note that all constraints need to be satisfied. If a generic class or method has more than 1 generic argument and you want to put constraints on more than one, you need to use another "where" for each argument you want to constrain. Just as a warning: Generics can be quite useful, but are often misunderstood. Many want to use them like polymorphism, however generics are somewhat the opposite of that. While deriving from a base class keeps the data of the base class but allows to overwrite functionality, generics actually keep the functionality the same while being able to exchange the data the function works on. Bound generic classes are usually incompatible with each other. So a List and a List are two completely separate types. In rare cases there can be exceptions with the right conditions (covariance / contravariance) but that are really rare usecases.
08:55 Well a lot is missing for it to be a video about all language features ^^. I know it can't really be comprehensive, but things that weren't really mentioned are:
delegates (essentially typed function pointers),
anonymous methods / closures, (ability to automatically capture variables in a scope object)
lambda expressions,
enums,
nameof,
all operators (there are a lot)
operator overloading in classes
type conversion operators
events,
CIL and the ability to decompile to other .NET languages
extention methods,
linq (I mean the LINQ syntax which is simlar to SQL, not the classes from the System.Linq namespace),
attributes (essentially static metadata that can be attached to almost everything)
params (essentially allows variable arguments as the last parameter of a method)
exceptions (try / catch / finally)
object initializer
nullable types
partial type declarations
ref / out (pass by reference)
indexer (allows a class to be used like an array or dictionary)
using statement (not to be confused with the using directive at the top. It's used to automatically dispose objects)
goto (Yes, C# has goto. Now forget that I mentioned it ^^)
reflection
Those are just some things of the top of my head. I only focused on language feautes, not framework features or classes.
Now I've spend already too much time on this post so lets wrap it up. There's still a lot missing. If you want to learn more about the syntax, look up "C Sharp syntax" on wikipedia.
I got a little lost at 4:26
(This is a bookmark so I can come back to it after a full night's sleep)
Yeah I tried to do this really fast but maybe too fast sorry
@@traintocode it is ok. I am just doing this until I get tired and confused, then sleeping and trying again. I am also new to coding
I found the grouping of constructors and deconstructors a little weird.
First off almost nobody writes deconstruct by hand, and secondly when people think of the pair of construction they usually think of dispose or finalisers, for cleaning up, rather than how to explode the type.
var value = 55;
var result = value switch
{
1 => "one",
2 => "two",
3 => "three",
_ when value > 10 => "greater than 10",
_ => "unknown"
};
Console.WriteLine(result);
That's one of the statements I didn't know, despite using C# for more than half a decade
This is for all c# versions ?
Some of these features will only be for later versions. C# is a very mature language that is currently on the 11th iteration, so no, many of these features would not have been present in version 1.
I hate var. its such a stupid thing to do and just makes it that little bit harder for someone else to glance at your code and know what is going on.
I very much disagree with what you say about `var` and implicitly typed variables at around 0:55. You make the very bold claim that implicit typing is good without any support of that claim.
Implicit typing is a tool, and just like all tools, there are good and bad ways to use it; situations that call for the tool and situation that said tool should be kept far away from.
Implicit typing should be used when, and only when, the inferred type is obvious to the reader and should be. If the inferred type is in any way obscured or non-obvious to the reader (for example, when storing the return value from a method or property in another class), the variable type should be explicitly declared. Note I said the reader, not the compiler and not the author. Just because the type is obvious to the author at the time of writing does not mean it will be obvious anyone else or to the author at a later time.
Ultimately it is all about legibility. Our code must be legible; illegible code is difficult to maintain and modify. Implicit typing is a tool to make writing code easier, but ease of reading always needs to take priority over ease of writing if the code is to have any longevity.
amen
Most C# does still use var, and there are good things about it, like reduced refactoring at the caller if a type changes. The reason it's generally still readable is that the IDE is good at providing the type information.
That said it's starting to move back away from var in some places, with nullable reference types and the new keyword e.g. T t = new();
Usually constructors and *destructors* are introduced alongside each other and not constructors and deconstructors. For one, many have heard of constructors and destructors but few may have heard of deconstructors and, as such, may not realise the subtle difference in the names and think the syntax demonstrated applies for destructors and not deconstructors! In fact, destructors are not even covered which makes it even less obvious that there is a difference!
Constructors and deconstructors are about turning variables into a class and turning classes into variables, so I thought they fitted together. I've rarely seen *destructors* actually used so didn't bother including them.
1:23 Why is implicitly typing things good?
The benefit of implicit typing is that it is easier to write, but you still get all the benefits of the static types. It's a matter of opinion though, do you prefer explicitly typed variables? Some people do
@@traintocode Basically you should do whatever your code guidelines say unless you're writing them.
이 ㄱㅅㄱㅅ 런 기술이라면 나도 할 수 있겠다는 생각이 듭니다.
Ok. So, why would you want a static function?
Static functions guarantee that the function does not depend on instance variables in a class and they can make functional programming styles a bit easier to stick to.
Didn't mention the all-important Lambdas but showed a bit of their syntax without saying what they were...
Sorry I was just trying to keep this fast C# has a LOT of features
C# has become too big, dumped it for GO and I will never look back 🥰
Go is a very streamlined language, something C# certainly is not! They are both great
don't do vars kids.
sounds more of a clickbait-y crash course than a comprehensive list of every single feature the language has (which would be believable if the video was around 2 days long)
It doesn't matter for me, it was exactly the kind of video I wanted. After many years not using C# I wanted to refresh my mind about its syntax
you're talking to other programmers only, inexperienced people get lost on those comparisons and references.
I had to condense everything to 10 minutes so a lot of prior knowledge is assumed yeah
"Every", and proceeds to list about a 2% of features
I went through a detailed 4 hour course over the past few days and then I watch this, it's ruining my knowledge so I stopped watching, this video is a great way to confuse people
It's very similar to Java, it's gonna be my next favourite programming language.