github AutoMapper/AutoMapper v3.2.1
3.2.1

This is a patch release to address the PCL issues of WPA81 only being available in VS2013 Update 2 RC.

As part of this release we had 4 commits which resulted in 3 issues being closed.
Patch release

Bugs

#499 Automapper 3.2.0 through Nuget is not CLS-Compliant

I commmented on issue #464 but it didn't open the issue also it's for 3.1.1 and this is for 3.2.0

Here is my comment

I just updated Automapper to 3.2.0 through Nuget and I'm getting errors that AutoMapper.Profile is not CLS-Compliant when I extend it in my VB.net project.

I see that the Common Assembly Info has CLS Compliance so unless Nuget is pointing to the wrong version I don't really know what's going on here.

#498 ForMember breaks ReSharper after upgrade to 3.2

In VS2013:

Mapper.CreateMap<S,D>()
          .ForMember ( d=>d.Something, o=>o.MapFrom( s=> s.Value ) );

indicates (red squiggle) that d.Something is not valid "Cannot resolve symbol Something". It complies ok and runs ok.

What am I missing?

Thanks

#381 ForMember angering ReSharper? - Non-existing PCL profile on client machine causing compile/R# errors

I'm trying to use the ForMember to add an ignore mapping to an object. ReSharper refuses to believe that ".ForMember(x => x.Thing, o => o.Ignore())" exists, though it's fine with using the string varient of that method. I'd rather use the former for obvious reasons, but seem to be stuck using the latter for now.

Note it, will COMPILE the other way, ReSharper just doesn't seem able to grok the Expression using the other one. Using 3.0.0 NuGet package.

Where to get it

You can download this release from:

latest releases: v10.1.1, v10.1.0, v10.0.0...
7 years ago