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

AutoMapper 6.1.1 very slow .cs file in Visual Studio Professional 2017 15.2 (26430.15) #2217

Closed
Ogglas opened this issue Jul 17, 2017 · 4 comments

Comments

@Ogglas
Copy link

Ogglas commented Jul 17, 2017

Hello,

I have a problem with my mapping file /configuration being very slow and lagging when adding new mappings to it. It contains around 40 mappings and I have seen this behavior before when the configuration file grows. VS does not lag in any other file even though they can consist of more lines of code.

With lagging I mean that it literally can take a second or two before what I type is displayed in Visual Studio. Before any Intellisense shows up it can take 5-10 seconds when it is normally instant.

I use ReSharper (Ultimate 2017.1.3) and when I disable ReSharper Intellisense it becomes a bit faster but still slow.

Do you have any fix for this?

Found one SO thread but it did not contain a good fix.

https://stackoverflow.com/questions/37513032/automapper-cs-file-extremely-slow-in-visual-studio-2015

@lbargaoanu
Copy link
Member

That's a question for a VS forum. You can split your config using profiles, that might help.

@Ogglas
Copy link
Author

Ogglas commented Jul 17, 2017

@lbargaoanu I think a lot of your users actually use Visual Studio and it only happens in a file containing AutoMapper configuration, I disagree this should only be a VS forum question and not something to look into.

@mchint01
Copy link

I am facing the same issue.

@lock
Copy link

lock bot commented May 6, 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 6, 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