A Microservices implementation journey — Part 1 

Is the repository pattern useful with Entity Framework Core? 

- Killing the utility class with premeditation
- Killing the utility class with relocation
- Killing the utility class with consolidation
- Killing the utility class with semantic types
- Killing the utility class with extension methods

The Problem

What they neglect to say is all that testability and persistence ignorance flies right out the window when you create a new ASP.NET Web Application using the MVC template and "Individual User Accounts" authentication. What you get is a single-layered application, tightly coupled to Entity Framework, that:

• Ignores the patterns that facilitate testing, including: the repository pattern, unit of work pattern, and dependency injection;

• Forces you to implement their IUser interface in your application’s User entity, thereby coupling it to ASP.NET Identity;

• Eliminates any clear separation between your entities, persistence concerns, and business logic. Persistence ignorance? Forget about it.

Thankfully, due to the extensibility designed into ASP.NET Identity, it is possible to ditch the reference to the Microsoft.AspNet.Identity.EntityFramework assembly and write a custom implementation that can address these and other architectural issues. Just be forewarned: it is not a trivial undertaking, and you’ll have to put up with some code smell that is baked into the Microsoft.AspNet.Identity.Core assembly. 

Flux vs. MVC: Comparing two Application Design Patterns
  

Strategy Pattern Implementations In C# 

Top 10 Programming Books Every .NET Developer Should Own

Exploring set(), get() and Object.defineProperty() in TypeScript