automapper-3

Given these two objects public class UserModel { public string Name {get;set;} public IList<RoleModel> Roles {get;set;} } public class UserViewModel { public string Name {get;set;} public IList<RoleViewModel> Roles {get;set;} // notice the ViewModel } Is this the most optimal way to do the mapping, or is AutoMapper capable of mapping Roles to Roles on its own? App Config Mapper.CreateMap<UserModel, UserViewModel>() .ForMember(dest => dest.Roles, opt => opt.MapFrom(src => src.Roles)); Mapper.CreateMap<UserViewModel, UserModel>() .ForMember(dest => dest.Roles, opt => opt.MapFrom(src => src.Roles

I am using Automapper for making a copy of an object My domain can be reduced into this following example Consider I have a Store with a collection of Location public class Store { public string Name { get; set;} public Person Owner {get;set;} public IList<Location> Locations { get; set;} } Below is an example of a store instance var source = new Store { Name = "Worst Buy", Owner = new Person { Name= "someone", OtherDetails= "someone" }, Locations = new List<Location> { new Location { Id = 1, Address ="abc" }, new Location { Id = 2, Address ="abc" } } }; My Mappings are configured as var

I updated my project to use Automapper 3.0.0 and now my TFS build is not succeeding. The error is the following: " ...System.PlatformNotSupportedException: System.PlatformNotSupportedException: This type is not supported on this platform IMapperRegistry. " Is there anyone that can help me resolve this issue. In the mean time, I am going to revert to previous version since that one seems to work fine. jni We had the same issue on our build server. MsTest seemed to remove DLLs it deemed unnecessary (note : this claim is only an educated guess). To fix it, add an explicit call to something in