A bit about the way to learn asp.net mvc?

Question

ASP.NET

Hello.
The situation is such that I set myself the goal of learning how to create applications on the web using one of the most popular technology now asp.net mvc 5 to achieve the goal, I set myself the task of learning:
1. С#
2. HTML 5 + css
3. T-SQL
4.Git/ Mercurial
5. java script
6. Angular.JS
6. and the actual technology of using asp.net mvc 5
I started my journey with the book // - Learning C # 3rd edition of Stillman - \\ which is often advised on the net, the question is, in his examples he uses visual studio 2012 in which he also heavily affects XAMl which takes a lot of time I want to learn C #, but for the web XAML is not very useful or maybe I'm wrong ? Another problem is that I use visual studio 2015 and a lot of things in XAMl from the book just don't work for me because a lot of things have changed since then.
Should I continue to learn C# touching on XAML if the goal is to program on the web, not the desktop, and is it worth learning from this book if XAML has changed a bit since the 2012 version and how relevant it will be, if not, could you recommend books for learning C# name under the web?

Answer 1

IMHO, it would be worth studying from Schildt or Troelsen. There, the language is served in its purest form, with console examples, without problems with the GUI at the very beginning. XAML is not needed on the web (because Silverlight, where it was used, is not very alive), it's true.
ASP.NET MVC requires HTML/CSS and basic SQL (there is an ORM in the form of EF, yes, but it's much easier to master once you know how it talks to the server). JavaScript can be taught in parallel. With angular, I would advise you to wait, jQuery instead (no matter what the hipsters say, it is almost everywhere now).
In general, it would be ideal to parallelize the study of C # in depth (according to Richerer, for example), databases and DAL (ORM - EF), ASP.NET MVC and web frontend, because it is more difficult to isolate from each other.
On Git, highlighting in a separate step is too much. Basic operations with Git can be learned in an evening, if necessary, read up in the process, maybe a couple more evenings are optionally allocated to "internals". In general, the need for it will appear when you make your first large pet project (that is, somewhere in the process of mastering ASP.NET MVC).
Adam Freeman "ASP.NET MVC X for professionals"
There is a version about MVC 5 on sale, but the version does not differ too critically from the version, so 4 will go for a start. This book is already purely about the web framework, something about the seasharp is overview there and only at the very beginning, you need to read it after having studied the base of the language . In addition, the author writes there about patterns (the notorious MVC and its history of development), techniques for writing unit tests and dependency injection (IoC / DI). The book is mega-cool for a beginner, but quite difficult, requires reflection and can become a desktop for a while.

Answer 2

WPF is a very separate and far from web thing.
So either asp.net and MVC or XAML and MVVM
Well, you should keep in mind that C # 7 is already in the yard, so you should focus on at least version 6 (this is certainly not the most critical, but still)