automapper

I am trying to map a DataTable to an object (DTO) using AutoMappers DynamicMap feature. DataTable dt; dt = new dalAllInvestors().InvestorNameSearch(investorNameSearch); // Look at DynamicMap - Urgent List<dtoAPISimpleInvestor> apiObject = AutoMapper.Mapper.DynamicMap<IDataReader, List<dtoAPISimpleInvestor>>( dt.CreateDataReader()); return apiObject; public class dtoAPISimpleInvestor { public int FirmID { get; set; } public string FirmName { get; set; } public string Type { get; set; } public string Location { get; set; } } dt returns 10 rows but when you look at the apiObject it returns no

This is probably quite straight forward for some, however I'm a bit confused and can't find a decent example. Say I'm using view models and my POST action takes in that view model. Typically I would do something along the following lines: [HttpPost] public ActionResult Update(UserViewModel uvm) { User user = Mapper.Map<UserViewModel, User>(uvm); _repository.Update(user); return RedirectToAction("Index"); } Although this isn't the full picture. The mapping would work fine, however if I were to just update what I've mapped then it'd get rid of valuable data in the database because of course in

At the moment, i got quite badly fashioned view model. Classes looks like this=> public class AccountActionsForm { public Reader Reader { get; set; } //something... } Problem is that Reader type comes from domain model (violation of SRP). Basically, i'm looking for design tips (i.e. is it a good idea to split view model to inputs/outputs?) how to make my view model friction-less and developer friendly (i.e. - mapping should work automatically using controller base class)? I'm aware of AutoMapper framework and i'm likely going to use it. So, once more - what are common gotchas when trying to

I am using virtual keyword for some of my properties for EF lazy loading. I have a case in which all properties in my models that are marked as virtual should be ignored from AutoMapper when mapping source to destination. Is there an automatic way I can achieve this or should I ignore each member manually? inquisitive You can create a mapping extension and use it: namespace MywebProject.Extensions.Mapping { public static class IgnoreVirtualExtensions { public static IMappingExpression<TSource, TDestination> IgnoreAllVirtual<TSource, TDestination>( this IMappingExpression<TSource, TDestination>

Can I use inheritance mapping in AutoMapper (v2.2) for maps with the same Source type but different Destination types? I have this basic situation (the real classes have many more properties): public abstract class BaseViewModel { public int CommonProperty { get; set;} } public class ViewModelA : BaseViewModel { public int PropertyA { get; set; } } public class ViewModelB : BaseViewModel { public int PropertyB { get; set; } } ViewModelA and ViewModelB are different representations of the same Entity class: public class Entity { public int Property1 { get; set; } public int Property2 { get; set

I have to classes Like class A { public int id {get; set;} } class B { public C c {get; set;} } class C { public int id {get; set;} public string Name {get; set;} } My requirement is to map id of class A to id of class C. Now what I was doing till now was: Mapper.CreateMap().ForMember(des => des.C.Id, src => src.MapFrom(x => x.id)); and it was working fine. Now seems like Auto mapper has changed their implementation. and I am getting warning as below: AutoMapper.Mapper.CreateMap()' is obsolete: 'Dynamically creating maps will be removed in version 5.0. Use a MapperConfiguration instance and

I'm using Mapper.DynamicMap() inside a generic method and would like to, without using .CreateMap() , ignore some any source values that are null. Is this even possible? If you want all source properties with null values to be ignored you could use: Mapper.CreateMap<SourceType, DestinationType>() .ForAllMembers(opt => opt.Condition(srs => !srs.IsSourceValueNull)); Otherwise, you can do something similar for each member. This will get quit tedious if there are a large number of properties. Srinath Subramani I solved it with DataMember property in destination type [DataMember(EmitDefaultValue =