Answer the question
In order to leave comments, you need to log in
What .NET technologies are worth learning now?
Hello dear community, this question has been raised more than one hundred times, but I will ask it again since all I managed to find was the answers ~2 years ago. I graduated from the university with a degree in information systems and computer technology, for the last three years I have been working in tech. support, this year I came to the realization that it was time to move on, I decided to try my hand at programming, the choice fell on C # (and in principle I didn’t break off, while I like everything), stocked up on books, already managed to evaluate the quality of translation into Russian and start reading original books with a translator, watch courses and gradually began to move in, tinkering mainly with the console, but at the moment it came to the realization that you need to choose a direction. you won’t go far on the console, and then the question arose, what to study? Information about the death of WPF has been circulating for more than a year, on the other hand, they write that there is a huge competition on ASP.NET MVC now. On the one hand, in the future I want to earn money and work as a programmer (I don’t dream of mountains of gold, I understand that the work is difficult and not always well paid), but on the other hand, I also program for myself (I have already decided on this, I want to work with Unity, the language just fits). Please advise whether it is worth spending time on learning WPF or is it better to immediately follow the path of learning everything and everything to work with ASP.NET MVC? (I understand that the matter will not be limited to one sharp, but I would not want to waste time). Or maybe besides WPF and ASP.NET MVC there is something else promising in this language? Thanks for the advice! On the one hand, in the future I want to earn money and work as a programmer (I don’t dream of mountains of gold, I understand that the work is difficult and not always well paid), but on the other hand, I also program for myself (I have already decided on this, I want to work with Unity, the language just fits). Please advise whether it is worth spending time on learning WPF or is it better to immediately follow the path of learning everything and everything to work with ASP.NET MVC? (I understand that the matter will not be limited to one sharp, but I would not want to waste time). Or maybe besides WPF and ASP.NET MVC there is something else promising in this language? Thanks for the advice! On the one hand, in the future I want to earn money and work as a programmer (I don’t dream of mountains of gold, I understand that the work is difficult and not always well paid), but on the other hand, I also program for myself (I have already decided on this, I want to work with Unity, the language just fits). Please advise whether it is worth spending time on learning WPF or is it better to immediately follow the path of learning everything and everything to work with ASP.NET MVC? (I understand that the matter will not be limited to one sharp, but I would not want to waste time). Or maybe besides WPF and ASP.NET MVC there is something else promising in this language? Thanks for the advice! Is it worth the time to learn WPF, or is it better to just go down the path of learning everything and everything to work with ASP.NET MVC? (I understand that the matter will not be limited to one sharp, but I would not want to waste time). Or maybe besides WPF and ASP.NET MVC there is something else promising in this language? Thanks for the advice! Is it worth the time to learn WPF, or is it better to just go down the path of learning everything and everything to work with ASP.NET MVC? (I understand that the matter will not be limited to one sharp, but I would not want to waste time). Or maybe besides WPF and ASP.NET MVC there is something else promising in this language? Thanks for the advice!
Answer the question
In order to leave comments, you need to log in
WPF is not dying at all. These are some strange rumors. For example, the latest version of the .NET Framework 4.7 included updates to WPF, and it's pretty impressive. And it will continue to develop. UWP (it has the same language as WPF: XAML) is usually tied to the Microsoft store and only requires the latest versions of Windows, as far as I remember. WinForm still exists, and it is not going to give up its positions yet. If you like this language, then work with them, learn new things. It will not work to study everything at once, the coverage is too large. Better to learn as you go. That's exactly what I do. When a new or optimal solution is needed, I look for it. The main thing here is to fill your hand in programming. WPF and ASP.NET MVC are different directions. The former are aimed at desktop solutions, while the latter are already web solutions. And then it depends on the tasks at hand.
I, too, have recently begun to dive into .NET technologies. And in order to understand where to start, I went through the vacancies and looked at what is required from a C # developer.
On average, for vacancies, they required:
1) Knowledge of C # itself
2) SQL
3) ASP.NET MVC
4) Enity Framework
5) WPF
6) Frontend direction
Based on this, I decided for myself what to study. Therefore, as advice, focus on vacancies.
Do not forget about the popularity of computer games, respectively, the demand for developers, for example, Unity 3d, is growing.
You shouldn't be talking about WPF so much) The desktop is still in demand, take a look at the vacancies. But the most popular web of course. Above the post, the correct list and priorities are there as they are, only xamarin mobile development was missed, but I would put it in last place.
I would suggest in web. There are a lot of vacancies, a lot of work, there are not enough developers.
And another upvote for the comment Fat Lorry.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question