Become a Full-stack .NET Developer - Architecture and Testing
Knowing how to architect and test ASP.NET MVC applications helps you build better apps. In Part 3 of the "Become a Full-stack .NET Developer" series, you'll refactor your app toward a better architecture as well as write unit and integration tests.
What you'll learn
As a .NET developer, you ought to know how to architect and test your applications - not only do these skills make you a more advanced developer, but they also help you build better apps. In this course, Become a Full-stack .NET Developer - Architecture and Testing, you'll learn how to do just that. This course is the third part of the "Become a Full-stack .NET Developer" series. In the previous two parts, you built a real-world mini social networking application for live music lovers. In this final part, you'll finish off the remaining use cases, modularize JavaScript code, and then refactor your application towards a clean, decoupled, and testable architecture. Next, you'll learn about programming against interfaces, and finally you'll write unit and integration tests for various moving parts. By the end of this course, you'll be able to create highly testable apps with better architecture, and you'll be one step closer to being a full-stack .NET developer.
Table of contents
- Introduction 0m
- Extracting JavaScript Code 4m
- Revealing Module Pattern 5m
- Refactoring Using Revealing Module Pattern 2m
- Cleaning the Init Method 2m
- Applying the DRY Principle 6m
- Better Separation of Concerns 2m
- Module Dependencies 6m
- Physical Separation 3m
- Optimization 3m
- Exercise 1m
- Code Review 5m
- Summary 1m
- Introduction 0m
- Extracting Queries 3m
- Repository Pattern 3m
- When to Use the Repository Pattern 2m
- Extracting Repositories 5m
- Extracting Queries with Eager Loading 5m
- Exercise 1m
- Code Review 5m
- Clean Architecture 3m
- Decoupling from Entity Framework 4m
- Unit of Work Pattern 4m
- Implementing the Unit of Work 3m
- Consolidating Dependencies 3m
- Summary 2m
- Introduction 1m
- Dependency Inversion Principle 4m
- Extracting Interfaces 4m
- Dependency Injection 3m
- Adding Ninject 5m
- Does Entity Framework Really Implement the Repository Pattern? 4m
- Package Dependencies 3m
- Restructuring the Application 7m
- Complexity Fallacy 2m
- Productivity Fallacy 4m
- Exercise 1m
- Refactoring Data Annotations 7m
- Summary 2m
- Introduction 1m
- Rules of Thumb 1m
- Setting up the Test Project 1m
- Mocking the Current User 5m
- Refactoring 3m
- First Test 5m
- Using ReSharper Live Templates 2m
- Second Test 4m
- Third Test 4m
- Fourth Test 1m
- Test the Behavior, Not the Implementation 3m
- Unit Test Refactoring 1m
- Testing the Domain Classes 3m
- Test Initialize 1m
- Exercise 0m
- Summary 1m
About the author
Mosh (Moshfegh) Hamedani is a passionate and pragmatic software engineer specializing in web application development with ASP.NET MVC, Web API, Entity Framework, Angular, Backbone, HTML5, and CSS. He started programming at the age of seven on a Commodore 64 and fell in love with it. His dream at the time was to become a software engineer so he could create a tennis game for himself in 3D! So this inspired him to pursue programming both academically and professionally. He has a Bachelor of Sc... more