AutoMapper Wiki & Documentation Rss Feed

New Comment on "Flattening"

MrChriZ — Sun, 19 May 2013 12:07:56 GMT

One problem I'm seeing is that say your customer domain object had the property CustomerName instead of just Name then the DTO needs to have the property CustomerCustomerName It would be good if Automapper could check the property isn't prefixed already with the class name.

New Comment on "Custom Value Resolvers"

jtu100 — Tue, 30 Oct 2012 12:54:58 GMT

Why is the advantage of using ResolveUsing instead of just UseValue within a ForMember call?

New Comment on "Custom Value Resolvers"

shailendrasute — Thu, 16 Aug 2012 18:36:37 GMT

Can i map two types to form a destination type? Basically I am looking at merging two types to form destination type. Please help.

New Comment on "Documentation"

AaronLS — Fri, 09 Mar 2012 19:37:46 GMT

The Automapper GitHub wiki doesn't appear to support search nor appear to be indexed. Even googling with a "site:github.com" constraint doesn't turn up anything more than bug reports. Makes it difficult to find documentation relating to certain functions/APIs in AutoMapper.

Updated Wiki: Home

jbogard — Sat, 24 Dec 2011 16:15:20 GMT

AutoMapper has moved to GitHub

AutoMapper has completely moved to GitHub:

https://github.com/AutoMapper/AutoMapper

The site can be found at http://automapper.org

All issues should be reported on GitHub. No issues will be responded to on CodePlex.

I can't turn anything off on CodePlex without deleting the whole site, which would be very confusing.

The latest downloads can be found at NuGet or at GitHub.

New Comment on "Custom Type Converters"

alhambraeidos — Thu, 17 Nov 2011 14:27:53 GMT

any sample for changed interface ITypeConverter I get this error now Error 7725 'BusinessFacade.Mappers.DecimalToNullableInt' does not implement interface member 'AutoMapper.ITypeConverter<decimal,int?>.Convert(AutoMapper.ResolutionContext)'

Updated Wiki: Documentation

jbogard — Fri, 02 Sep 2011 22:44:00 GMT

AutoMapper has moved to GitHub

AutoMapper has completely moved to GitHub:

https://github.com/AutoMapper/AutoMapper

The site can be found at http://automapper.org

All issues should be reported on GitHub. No issues will be responded to on CodePlex.

I can't turn anything off on CodePlex without deleting the whole site, which would be very confusing.

Documentation is on the wiki: https://github.com/AutoMapper/AutoMapper/wiki

Updated Wiki: Home

jbogard — Fri, 02 Sep 2011 22:37:18 GMT

AutoMapper has moved to GitHub

New Comment on "Documentation"

TdeRoo — Thu, 01 Sep 2011 04:21:56 GMT

Somehow the subjects on this page are not hyperlinks, only the first item is. This makes it hard to read the documentation which is there.

New Comment on "Custom Value Formatters"

TdeRoo — Wed, 31 Aug 2011 09:51:40 GMT

Does this mean that I can supply a <System.ComponentModel.DataAnnotations.DisplayFormat(DataFormatString:="{0:dd MMM yyyy}")> attribute to a string property in a class and that it will use the appropriate ToString(format)? I have several classes which implement IFormattable so that would really help I think.

New Comment on "Configuration Validation"

kpetersen — Wed, 22 Jun 2011 16:39:36 GMT

If you're stuck using VB like me, this is the syntax for Ignore() : Mapper.CreateMap(Of Source, Destination)() .ForMember(Function(dest) dest.SomeValue, Sub(opt) opt.Ignore()) Note the Sub instead of Function.

New Comment on "Custom Value Resolvers"

paul07481 — Sun, 19 Jun 2011 08:18:07 GMT

Is it possible to make this fluent or is there a better way to do the following? For example if I have a set of dates stored in UTC in my domain model and I need to convert them to local time for my view models it would be nice to write one custom resolver to do the date transformation and then do this every time I have a date in the domain model: Mapper.CreateMap<Order, OrderModel>() .ForMember(dest => dest.OrderDate, opt => opt.MapFrom(m => m.OrderDate).ResolveUsing<TimeZoneResolver>()) At present I think I need a new custom resolver don't I? Thanks for a brilliant time saver by the way.

New Comment on "Getting Started"

clee2005 — Mon, 30 May 2011 18:42:42 GMT

Well done sir! Saved me a boatload of time... it's very smart!

New Comment on "Custom Type Converters"

t316 — Wed, 25 May 2011 14:10:59 GMT

I am a newbie and am looking for some advice on a design pattern for something very specific: I am using Asp.Net MVC3 and EF 4.1 where I have an Email entity: int Id; string EmailAddress; I also have a Referral entity: int Id; Email ReferredEmail; I also have a ReferralVM: string EmailAddress; I use the ReferralVM for Create and Edit actions - this way I can use regular expression validators for the email address. When using AutoMapper in the create and edit controller action, I want to map the ReferralVM to a Referral object, which in turn means that the string EmailAddress needs to be looked up in the db and either and existing or new Email entity needs to be returned to set the Email property of the Referral class. During the "auto mapping" how can I get an instance of my EF database context? If I new up one then the Referral and its Email property will be from different contexts, right? I need to pass through in to the guts of the auto mapping functionality a reference to an EF data context. What's a good approach for solving this problem? Thanks

New Comment on "Nested Mappings"

shipon_eye — Wed, 27 Apr 2011 20:48:25 GMT

Hello! Can I configure the case sensitiveness for mapping? How can i handle it? Please suggest me. Thanks

New Comment on "Custom Value Resolvers"

adamtolley — Wed, 20 Apr 2011 19:17:38 GMT

Mapper.CreateMap<Source, Destination>().ForMember(dest => dest.Total, opt => opt.MapFrom(src => src.Value1 + src.Value2)); works just as well for the first example; Is there a reason to use Custom Value Resolution instead (other than as a way to specify something as a method rather than in a lambda)?

New Comment on "Custom Type Converters"

adamtolley — Wed, 20 Apr 2011 19:04:22 GMT

@danthman : If the design requires different conversions in different places you can get specific with your .ForMember() options when mapping specific types. It seems supplying a type converter is useful for defining a global conversion practice (which can be overridden by specific mappings). Check out the "Projection" feature.

New Comment on "Projection"

mahichr — Fri, 11 Mar 2011 20:29:35 GMT

@jpark2 For "Expression does not produce a value" error in VB.Net all you have to do is use Sub(opt) instead of Function(opt). The above example would look something like this. Mapper.CreateMap(Of CalendarEvent, CalendarEventForm)(). ForMember(Function(dest) dest.EventDate, Sub(opt) opt.MapFrom(Function(src) src.EventDate.Date))

New Comment on "Configuration Validation"

ntziolis — Thu, 24 Feb 2011 10:46:18 GMT

I second that, it needs to be much clearer that a full mapping is not required when AssertConfigurationIsValid is not called. Maybe make make the assert configuration required, but add an IgnoreAllNotMapped methods to the MappingExpression, because usually you end up mapping 2 properties and adding ignore statements for all the others in order to be able to validate the configuration.

New Comment on "Roadmap"

krokonoster — Wed, 19 Jan 2011 06:31:43 GMT

Anyone used Automapper where the destination type have a dependency that need to be resolved. At present, this is passed from the controller (also having this dependency, and resolved here) to the ViewModel constructor. Changing this logic is not an option, and CreateMap<Source,Destination>() won't work, since Destination expect this depedency instance.