Programming

People seem to be misunderstanding your question. It doesn't sound like you are lacking educational resources to learn C# but a lack of reasons. It sounds like you have been learning by getting you're hands dirty with foss software.

C# is a sort of "enterprise-grade language" like Java. It's meant for large applications developed by one or more teams for almost exclusively commercial purposes. If you want to learn it, deeply, you'll have to come up with an excuse to write in it. A game is probably the best choice for this. Then learning c# is learning how to make your game.

If you're looking for open source C# software to hack on you can try anything from the *arr stack. (Sonarr, radarr, lidarr).

Start with "absolute beginner" courses. Here's one from Bob Taylor. He puts out a lot of good stuff.

Sit your self down and study it for a good bit, then build some things. https://youtu.be/0QUgvfuKvWU

I learned it because I had to write a WPF desktop application, so you could start with WPF tutorials. I was already very familiar with Java, which is very similar, so it wasn't too hard. Last time I used it was in Unity. You might want to find a good free online course for C# to get a good grasp of C#/Java's style of OOP, design patterns, and all that kind of stuff.

You think Bash is the easiest language? I have to Google the syntax every time i need to write and IF statement!

one of the most popular languages, used in one of the most popular game engines, has no learning resources?

Press X to doubt

Starting with Visual Studio (not code) helps a ton. Make a simple winforms application with a button and some labels and you will start to see how it 'starts up' from program.cs to your form.

When I was learning c#, I found the .Net framework tutorials available on freecodecamp to be good.

Also, using the Jetbrains Rider IDE (assuming this is for private non-commercial purposes, as per the terms of their free license) rather than VSCode or Visual Studio. VSCode is still lacking in features when it comes to c#, and Visual Studio probably makes more sense if you're already accustomed to c# dev.

The heck you're talking about? There's a ton of free resources to learn the basics.

https://dotnet.microsoft.com/en-us/learn/csharp official Microsoft learning resources.

https://dotnettutorials.net/course/csharp-dot-net-tutorials/ for C# basics and .NET framework (which is backend standard).

For game engines you need specific tutorials in those engines.

An IDE with auto-complete would help a lot.

Don't learn a language unless you need to use it for something.

That's why you're finding it hard. If you needed to program a game, decided on Unity, and had a specific thing to do, it would be easy to figure out how to do that in C#.

1. Start writing a small game in Godot using GDScript (basically Python)
2. Use the Godot docs to read about C# alternatives to GDScript as you go, compare them and see how they differ
3. Translate bit by bit of your game to C# using the docs
4. Congrats, you have written a game in C#

This is how I feel about music

Start with the goal to create something, be it a console app, website, web api, or game. It's hard to just study a language abstractly and learn it. Use the Microsoft Learn documentation as reference, and look for open source .NET projects on GitHub to get different perspectives on how to build things with .NET. There is a free course on freecodecamp that will get you started by building an app, and I believe it was done in partnership with Microsoft

1. Make a text adventure game that runs in the console.
2. Tic tac toe in the console.

Then if you want to go for a GUI web app with react use "dotnet new react" and create a to-do list with a client/server setup.

If you want to learn to make games you could make a tic tac toe again but with a GUI in Godot.

Once that's done make tetris.

You research what you need right before you need it and use it immediately so it sticks better. You'll need to get comfy with typing systems and I recommend using an IDE like Rider or Visual Studio to program it since they help out a lot.

It sounds like you'd benefit from having a project in mind. I always learned programming languages by building something I wanted, or by tinkering on someone else's project.

Microsoft produces a plethora of good learning materials if you're struggling with the basics or specific concepts. I recommend their C# for Beginners course to get a good overview of real C#.

Once you have a good handle on the basics, I would echo others' advice that having some kind of project or goal to work towards is the surest path to learning, because you have external motivation to use what you're learning and look up things as you need them. Is there some reason you chose C# specifically as your next language, maybe for game dev, web dev, or Windows apps?

Check out this reference (not mine): https://gist.github.com/DanielKoehler/606b022ec522a67a0cf3

The first difference that I would point out is c# use of static typing, where python is dynamic. This author is using the var keyword to avoid specifying a type for variables. The type is, instead infered by the code that follows the equals sign.

The next main difference is the use of whitespace. Python is very whitespace aware, it uses indentation and line breaks to organize code. C# is whitespace agnostic in most cases and separates blocks of code using curly braces {...}, statements must end with a semicolon;

In C# collections are organized by how the data is accessed and whether elements can be added or removed. Arrays are initialized with a set of items and can't be made longer, a List can be added to and can be removed. The key point is that all items in a collection are of the same type.

Complex objects (that have properties and methods) can be structs, classes, or records but they all basically do the same thing and interact in the samish way. You have to use the new keyword to make a new instance.

Classes and records can inherit from another where as structs cannot. Properties must have a type, methods must return a type or void. Method parameters must be typed, when calling a method the provided parameters must be of the proper type.

An interface describes requirements an implementing class, record or stuct must meet (i.e. properties and methods). You can't make a new interface, it's more of a qualification.

I hope this helps some

Tim Corey on YouTube has excellent beginner C# material. I would start there.

I learned C# from the Aurora guide book I picked up with Neverwinter Nights back in the day.