Hi! I just decided to study C# and I am a bit lost.
The course I’m following is teaching C# using the .NET Framework, is there much of a difference from it to .NET 5.0, by that I mean, can I still follow a course teaching C# using the .NET Framework even if I’m running .NET 5.0?
Finally, in your opinion, should I follow the course and learn C# using the .NET Framework (I heard it’s obsolete), or should I just go for the .NET 5.0?
.NET Framework only runs on Windows. .NET Core (the “Core” was dropped for 5.0) is cross-platform and runs on most OSs.
Most of the APIs are the same but there are some differences. Up to v3.1 the major focus was supporting most of the .NET Framework APIs.
It cant hurt to learn Framework, but you might run into problems if you’re not on a windows machine / cant install Framework. Depends entirely on what the course dependencies are.
Thanks a lot for explaining, makes things easier for me to digest.
I guess I will just keep using the .NET Framework for now then, I’m on Windows and I doubt I’ll be switching OS too soon.
When I learn a bit more I might switch to .NET 5.0
There won’t be a huge difference in what you learn, so starting with .net framework or .net core will be fine. The differences are a bit more esoteric, as long as you’re using the newer versions of C#.
.net 5 is basically a renaming of the next version of .net core which now unifies the two platforms. There are legacy things which are not supported moving forward, but if you’re getting started you likely won’t care.
Thank you! I will be using .NET Framework for now and I may switch to .NET 5.0 when I feel more comfortable with the language/framework.
You haven’t said why you decided to learn C# but I’ll assume it’s for career purposes.
I’d look for a course that focuses on .net core. There may be jobs for .net standard developers where you are but here (UK) they’re reducing as a proportion of the overall .net market. Anything you learn will probably work the same in standard, or if it doesn’t you can certainly find a way of doing it, though it may be less elegant.
C# devs
null reference exceptions