Wrap Up
The Thrilling Conclusion and the Start of Something New
We've reached the end of the C# tutorials, but this only marks the beginning of the start. From here, the next step is to continue to another tutorial set. Perhaps the MonoGame tutorials are your next step if you're ready to start making games.
Of course, even our C# journey isn't over yet. This crash course is only enough to get us started. You'll continue to learn more about C# as you go.
While we're on the subject, if you're looking for a more in-depth treatment of C#, please consider my book, the C# Player's Guide. It covers everything here in far more depth, covers way more topics, and does so in a casual and fun way. It also includes a whole mountain of challenges to work through, which help solidify what you're learning.
One of the bigger challenges ahead of you is learning to use all the many types that come as a part of C# (called the Base Class Library). If you're wondering how one of these types works, Microsoft has very good documentation on each of these classes, structs, interfaces, and other types: https://docs.microsoft.com/en-us/dotnet/api/.
Don't be a stranger, either. Feel free to drop in the Discord server or post in the forum if you want to discuss something specific.
If you have suggestions to improve these tutorials or have suggestions for other tutorials, I'd love to hear about that too.
Good luck on your next adventure!
Thank you for the tutorials! You're awesome! c:
RB, thanks a lot for creating this C# Crash Course. It has certainly been impactful and stimulating to my learning process. Cheers!
Really wish I'd found this tutorial set a year or 2 ago. As a front-end designer who knew nothing about programming, I'd always ham-fisted (Or beef-fisted(?), being across the pond…) my way through jQuery in a procedural (Spaghetti) style to get the View to do what I wanted.
2 years ago (and 3 days if I'm being pedantic) I got dropped In the deep end of our IT dept as the previous manager/.net dev left without serving his notice, and had coincidentally not done any planning or development work regarding a major update with a 3rd party api. I stepped up and said let me try something in PHP (the only back end language I had any clue of at the time) while they tried to find a replacement, it took some googling but I got there in the end!
Fast-forward 2 years, we had a replacement who came and left in the blink of an eye (because as a developer, I could out-code him?!) and so I asked for the position. Since then I've been diving through the legacy code here, written in .NET or VBScript (Joy…) but had never had anyone to tell me the basics, until now ;)
This is the first tutorial series that I could actually follow, usually it gets complicated quickly and then someone starts talking about Dependency Injection and I just give up. I just want to know why I need to put the "Static" keyword on my method in order to get the solution to build! Stack Overflow only gets you so far but if extra reading is required you'll end up on Microsoft's Technical Documentation which assumes a greater level of understanding than I currently possess.
In short, Thank you for taking the time to write a basic guide for people who have little understanding of programming as a science (or art in some cases!). I've got a lot of refactoring to do….
10/10 amazing.
Post preview:
Close preview