Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapper.GetAllTypeMaps() obsolete #1252

Closed
rafakwolf opened this issue Apr 29, 2016 · 6 comments
Closed

Mapper.GetAllTypeMaps() obsolete #1252

rafakwolf opened this issue Apr 29, 2016 · 6 comments

Comments

@rafakwolf
Copy link

This method is obsolete -> Mapper.GetAllTypeMaps()
What can i use instead ?
Sorry for the question here, thanks.

@jbogard
Copy link
Member

jbogard commented Apr 29, 2016

Use Mapper.Configuration.GetAllTypeMaps().

@rafakwolf
Copy link
Author

rafakwolf commented Apr 29, 2016

@jbogard i'm sorry but , Mapper.Configuration is obsolete to, and the method GetAllTypeMaps() don't exists. :|

Thanks

@jbogard
Copy link
Member

jbogard commented Apr 29, 2016

Have you tried the myget feed? It's not obsolete there, and the method does exist there too.

@rafakwolf
Copy link
Author

OK, i will try myget, thanks

@MrDesjardins
Copy link

I had a similar problem after migrating with the new version that obsolete static methods.

I was using Mapper.Engine.ConfigurationProvider.GetAllTypeMaps() which wasn't working after the update. I meant by not working that it wasn't able to get the type maps from the MapperConfiguration.

To fix it, I had to get the configuration and use

            var config = new MapperConfiguration(cfg =>
            {
                foreach (var profile in profiles)
                {
                    cfg.AddProfile(profile);
                }
            });
            config.CreateMapper();

and use

config.GetAllTypeMaps()

Hope it helps!

@jbogard jbogard closed this as completed May 19, 2016
@lock
Copy link

lock bot commented May 7, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants