To answer your specific question I will speak more generally about your architecture. The architecture you’ve devised for your project is subtly different from a typical architecture used with DDD. While the way you’ve partitioned responsibilities is typical, in DDD, domain classes aren’t responsible for their own persistence. In fact a mantra of DDD is … Read more
I just ran into this problem and came to know that You need to include following Nuget package AutoMapper.Extensions.Microsoft.Dependencyinjection
If you want/need to stick with the static implementation in a unit testing scenario, note that you can call AutoMapper.Mapper.Reset() before calling initialize. Do note that this should not be used in production code as noted in the documentation. Source: AutoMapper documentation.
Have you tried to use the Map method that way: Mapper.Map<DestinationClass, SourceClass>(object to convert) ? With the 2.2 version of AutoMapper, this is how we use it and it works fine for us.
It’s OK to pass the DTO to the view. If you need to change or enhance the DTO then create a ViewModel. A common scenario would be to add links. It’s also OK for the ViewModel to reference the DTO as a complex property.
I much prefer avoiding the older Static methods and do it like this. Place our mapping definitions into a Profile. We map the Root first, and then apply the mappings of the Nested afterwards. Note the use of the Context. public class MappingProfile : Profile { public MappingProfile() { CreateMap<Root, Flattened>() .AfterMap((src, dest, context) => … Read more
AutoMapper allows now (I am not sure, since when) to map properties with private setters. It is using reflection for creating objects. Example classes: public class Person { public string Name { get; set; } public string Surname { get; set; } } public class PersonDto { public string Fullname { get; private set; } … Read more
You don’t need to setup your mapping for collections, just the element types. So just: Mapper.CreateMap<X, Y>(); Mapper.Map<X[], Collection<Y>>(objectToMap); See here for more info: http://automapper.codeplex.com/wikipage?title=Lists%20and%20Arrays&referringTitle=Home
On automapper where you create the Map you can specify additional processes for specific members of the destination type. So where your default map would be Mapper.Map<Domain.User, UsersDetailsViewModel>(); there is a fluent syntax to define the more complicated mappings: Mapper.Map<Domain.User, UsersDetailsViewModel>() .ForMember(vm=>vm.UserName, m=>m.MapFrom(u=>(u.UserName != null) ? u.UserName : “User” + u.ID.ToString())); Here the ForMember takes … Read more
You are using : Mapper.CreateMap<Source, Destination>() .ForMember( dest => dest.OutputData.Cars, input => input.MapFrom(i => i.Cars)); This won’t work because you are using 2 level in the dest lambda. With Automapper, you can only map to 1 level. To fix the problem you need to use a single level : Mapper.CreateMap<Source, Destination>() .ForMember( dest => dest.OutputData, … Read more