We have a problem with project files, which is annoying.
Example:
We have a solution with projX and projY that reference the log4net assembly .
Say for example. someone moves the assembly file and updates the link only in projX +, and then commits without detecting the missing assembly - then the link is missing in projY .
The next time I check and open the solution, projY has a link marked VS2010 as missing, with a little exclamation mark. So far, so good.:)
Problem:
Now, if I create a solution assembly, the assembly link is magically updated in projY to specify the projX BIN folder ! (In this case, projX must be created before PROJY)
It seems that VS2010 is looking for our decision tree and automatically adds the assembly if it can find the corresponding file.
Good feature, but also a little dangerous and very wrong navigation. For example, the assembly may have a path pointing to another bin folder of the project.
Question:
Is there a way to disable this behavior and just get a compilation error that prevents the build?
Notes:
- Recently, we have switched to using NuGet.
- We defined our own output folder -> the files are not placed in Bin \ Debug, but in .. \ output.
[EDIT]
Updated example for clarity.
[EDIT]
articale, , VS2010 , GAC. GAC. http://blog.scrappydog.com/2010/07/bug-tfs-2010-outsmarts-itself-and-auto.html
[EDIT]
, . , VS " ", - bin. . .