Skip to content


Subversion checkout URL

You can clone with
Download ZIP


ReSharper references dlls in bin/debug #5

citizenmatt opened this Issue · 0 comments

1 participant


Fairly reliable way to reproduce:

  • Project A references a package assembly
  • Project B references the same package assembly
  • Build both, then delete the reference to the package assembly from project B
  • Close and reopen the solution, use the quick-fix to reference the assembly and import a type - this will most likely be the file from bin\debug

ReSharper keeps a list of each assembly it sees, and a list of file locations it's seen the assembly at. The problem is that the order of this list is important - the quick-fix adds a reference to the first location in the list. If that location is bin\debug, you get a bad reference. I can't see what's causing the ordering to collect bin\debug before the assemblies in the project references, but it's a fairly reproducible scenario.

@citizenmatt citizenmatt was assigned
@citizenmatt citizenmatt closed this issue from a commit
@citizenmatt citizenmatt No longer references dlls in bin folders
ReSharper tracks the file location of each usage of each assembly. The
list of file locations is in an undefined order, and the reference
quick-fix uses the first. If the first is in a bin folder, we don't find
it in NuGet. We now check all file locations for a NuGet package. Fixes

Also tested in ReSharper 7.1, and bumped version to 1.0. Fixes #5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.