Throughout the previous chapters of this book, you have gotten familiar with many major topics related to ASP.NET MVC, and you have learned how to build your own ASP.NET MVC applications. However, some common topics not yet covered are necessary to understand when you implement a project.
Like ASP.NET WebForms, ASP.NET MVC is a Web development technology that is designed to provide a means for building Web applications, and each of them is built to address specific requirements. ASP.NET WebForms treats these requirements in its own way based on its infrastructure and development model (which is based on controls and events), but in ASP.NET MVC these concepts are implemented in a different form (which gives you a greater separation of concerns). You see an example in Chapter 15, which talks about authentication and authorization, where many of the concepts are constant between these two technologies.
The two technologies have some topics in common because as we discovered, both are using some constant parts of ASP.NET core API. However, even these similarities may have slightly different implementations in higher levels in each technology. So we can classify the differences between these two technologies into two groups:
Some ASP.NET concepts and techniques that are available in ASP.NET MVC that have only minor differences between their implementation in ASP.NET WebForms and their implementation in ASP.NET MVC
Some Web development techniques ...