Exception when changing build configuration
Hi,
Am I the only one having exceptions thrown everywhere (assembly != null) whenever you change the build configuration?
I have found, that having different output directories for your assemblies, make ReSharper choke, probably because it finds multiple assemblies with the same name in the bin-folder.
If I configure the build to output in the same directory (the bin\ folder), ReSharper behaves, but if not, it freaks out!
This is very annoying, and happens in every version of ReSharper I can remember.
Please sign in to leave a comment.
I often see exceptions during config changes - I try to remember to report them but, like you, it feels like they've always been with us.
Hello Kenneth,
Does this happen with build 2117 as well? Thank you!
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Yes it does. In previous versions (5.0, 5.1) ReSharper would simply complain about ambigous references everywhere, and there was nothing to do but either suspend/resume ReSharper or restart Visual Studio, but now it just throws exceptions instead.
I'm not completely sure how to reproduce it, but in every new solution I make, multiple build configurations would make ReSharper throw exceptions, if I change between them (if the output path have different locations (ie. bin\Debug\ and bin\Release\).
Kenneth
Any news on this issue?