3.1.1 not CLS-Compliant #464

Closed
jnapier opened this Issue Feb 21, 2014 · 3 comments

3 participants

@jnapier

Automapper 2.X was CLS-Compliant. Is there a reason that 3.1.1 is no longer CLS Compliant? Can the next version be CLS-Compliant again?

@jbogard
AutoMapper member
@jnapier

Using Dependency Injection to inject IMappingEngine into services to Map as opposed to the static Mapper type.It's easier to mock IMappingEnging than static Mapper. Now my classes that have IMappingEngine dependencies are not CLS compliant anymore.

@jbogard jbogard added this to the 3.2.0 milestone Feb 26, 2014
@jbogard jbogard closed this in c038178 Feb 26, 2014
@jbogard jbogard added the Improvement label Apr 15, 2014
@CalvinRodo

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment