About assembly analysis Follow
I'd like to ask a few questions around assembly analysis in ReSharper.
ReSharper has always slowed down the build process, that's a fact. However, I have the impression that it's much worse in R# 6 EAP than it was in R# 5.1. Still, I think there could be several optimization paths, judging by what is shown when you click on "processing assemblies":
- Why is ReSharper analyzing an assembly that has just been built when this assembly is only referenced as a "project reference" within the solution? I personally don't care about being able to navigate to the generated assembly. Can there be an option for this? It would really improve build times.
- Each reference of the newly built assembly seems to be reanalyzed. During a build I can see that R# is processing assembly references its already aware of, since they are used by opened projects. This can sometimes last 5-10 seconds eating CPU for a reason I don't understand. Can you elaborate about the reason of this behavior? If 1) can be toggled off, will 2) be off too?
Please sign in to leave a comment.
This problem should get fixed in the next nightly build of ReSharper 6. Could
you please install that build when it comes out and check if it works better?
Senior Support Engineer
"Develop with pleasure!"
Thanks for your answer. Unfortunately there is no new nightly build today. As soon as the next one comes out, I'll get back to you.
Thanks, the problem seems resolved in latest builds. Build is still quite slow but it's noticeable that less analysis is done while building, thank you.