A practical guide to improving the design of an ASP.NET MVC applications by applying the rules of refactoring
☑ Reviewing existing applications for code and architectural improvement
☑ Making the safety net of unit test cases before you start modifying application code
☑ Identifying and applying design patterns in complex scenario
☑ Separating out UI requirements from server side code
☑ Writing applications that are easy to understand, change, and maintain
This course starts from the ground up. It starts with a ground-up and talks about the SOLID principles.
The course then picks up the pace and introduces an ASP.NET MVC Application written with the intention of demonstrating the capabilities of the Entity Framework.
Refactoring is making small changes to the application without affecting the observable behavior of the application and at the same time improving the design of the application.
Why Refactoring?
A lot of developers complain that they are familiar with most or all of the techniques of refactoring. They have knowledge of Object-Oriented Programming and Design Patterns as well. But when they work on their projects they hit a roadblock. After some point, it gets very difficult to write clean code. Code that is flexible, extensible, and at the same time is easy to understand, change, and maintain. In complex business applications, it is extremely difficult for most to apply these rules.
When the applications are older and they are supposed to port it to newer platforms it gets more challenging.
This course takes a practical approach. In an existing application that is significantly complex, the course adds test cases which becomes the safety net. The application is then refactored using the SOLID principles and other design patterns which improves the design of the application.
English
Language
Refactoring Hello World
Why Refactoring?
What is Refactoring?
Hello World
SOLID Principles
Single Responsibility Principle
Dependency Inversion and Interface Segregation Principles
Open-Closed and the Liskov-Substitution Principles
Single Responsibility Principle – Again
Inversion of Control using Unity