Use code PATTERNS20 at checkout to get 20% off our 3 Design Patterns in C# Bundles: https://bit.ly/3YPiHLD
Subscribe to my weekly newsletter: https://nickchapsas.com

Become a Patreon and get special perks: https://www.patreon.com/nickchapsas

Hello, everybody. I'm Nick, and in this video, I will explain why I don't think you should be using AutoMapper or almost any mapper in .NET and instead use manual mapping.

Workshops: https://bit.ly/nickworkshops

Don't forget to comment, like and subscribe :)

Social Media:
Follow me on GitHub: https://github.com/Elfocrash
Follow me on Twitter: https://twitter.com/nickchapsas
Connect on LinkedIn: https://www.linkedin.com/in/nick-chapsas

Keep coding merch: https://keepcoding.shop

#csharp #dotnet

Nick Chapsas

The post discusses the drawbacks of using AutoMapper and other mapping libraries in .NET, advocating for manual mapping instead. It highlights issues such as the introduction of runtime errors, complexity, and debugging difficulties when using these libraries. The author suggests using simple extension methods for mapping and emphasizes the importance of maintaining control over the code. Alternatives like compile-time libraries are mentioned but manual mapping is preferred for its simplicity and reliability.

Stop Using AutoMapper in .NET

We use AutoMapper at work and yeah, while the concept sounds practical, it does add another layer of complexity to everything, especially when it’s used for mapping ALL models between the frontend and the database…even ones with just a couple properties.

Yes please, AutoMapper should not be used ‘by default.’
I have reviewed numerous test tasks where AutoMapper (and ‘clean architecture’) was added to simple APIs without justification.
This only pollutes and overcomplicates the code without reason