Transition. From ASP.NET To ASP.NET MVC?

Question

ASP.NET

Asking exclusively experienced in ASP.NET MVC .
How long will the transition to ASP.NET MVC take , now they have offered another site, and I don’t know whether to learn ASP.NET MVC in ~ a week or start doing it on the same web. forms.
The pattern itself has been studied, there is experience (in other languages).
Two stages are of interest:
1. When it is already possible to slowly develop on ASP.NET MVC, more or less understanding how everything works. Of course, with bugs, crutches, in general, gov..-code
2. When you already know everything like a prof. and easy to adapt to any circumstances. Also, keep supporting. + use of multithreading, Entity, and many more. (It's different for everyone here. How are you?)
I know, I was delayed, it's high time to switch to a new technology ...
Are there those who immediately stepped over this stage? (immediately MVC)

Answer 1

Good afternoon!
From my own experience, I can say that ASP.NET MVC seemed to me more understandable, simpler, clearer and more transparent than "those terrible" (pardon the subjective opinion) ASP.NET WebForms. I started my acquaintance with ASP.NET from WebForms, then switched to MVC - my happiness knew no bounds.
According to your "stages":
1. When you learn ASP.NET MVC from the book "ASP.NET MVC x for professionals" (x is the version number).
2. Everything here is very subjective and depends on the projects themselves and their tasks. You can write 15 projects in MVC, but they will all be the same. And you can write 2 projects in MVC, but at the same time they can differ so much that having only a couple of projects behind you, you will already know by heart the whole MVC, C#, Entity Framework,
You can, of course, sculpt projects on WebForms all your life, but I would strongly recommend that you do all new projects exclusively on MVC. Moreover, in a week you can easily study it from a book (subject to a full working day).

Answer 2

ASP.NET MVC itself, as a beginner, seemed to me easy to learn and use. It is much more difficult to build correct work with models (representations of objects). Already drowned in the study of Framework Entity, Ninject and Moq, which I chose to implement the "Repository", "Abstract Factory", "Strategy" patterns ...
In general, if you implemented the project in ASP.NET, then transfer it to ASP.NET MVC will not be difficult for you.