Using AutoMapper in POCO?

Question

I currently have a POCO class in my ASP.NET MVC project that handles all the business logic. No links to other projects or third-party builds.

I also use AutoMapper in my other projects to facilitate comparison between models / view objects. This is a fantastic tool and saves me considerable time when I make changes to the fields at this facility.

However, in my POCO class, there are several code segments that map between objects. The goal of the business is to obtain objects from one data source and update another data source. Here I manually map, and I find it annoying to go in and set up this mapping when I could use AutoMapper instead.

Is this a good idea or a bad idea to use AutoMapper in my business logic project? Why?

Answer 1

'Answer your question with a question.

AutoMapper ? , , AutoMapper.