Geek Answers Handbook

How to stop visual studio from updating assembly links?

In our environment, we have a Lib folder that contains various third-party assemblies referenced by our projects. For example, Enterprise Libary and Elmah.

Sometimes the developer does not receive updates in this folder. When a developer loads a project that cannot find the assembly in the expected folder, Visual Studio automatically finds another copy and updates the links to the project.

The problem occurs when the developer checks in the project and pinches everyone else.

Is there any way to stop visual studio 2008 from doing this?

UPDATE: I wanted to add that we use TFS for version control.

+5
source share
4 answers

. ( !)

( -GAC) dev, W: . DLL, ( ) . DLL , license.dll, Infragistics.

, (EntLib, Infragistics ..), , W:. . . .

( ) DLL - , .

( ), VS . ( 5 6 , ), , . , , - , CI- , .

- , . CruiseControl.NET, NAnt , CI .

, , , ( Demon Spawn, . ) . ( Demon Spawn ). - , 5-6 . , .

... - , DLL, dll.refresh.

+4

, , DLL .

ThirdParty, , ajax $/ThirdParty/Microsoft/AjaxToolkit/( ). , , .

dll , , , DLL.

+2

, .

, , , "HintPath". , GAC.

, ( ), .

+1

, , . : 1. GAC, . 2. BIN. . 3. Copy Local = false AND Specific Version = False. , , , BIN, . , VS . "dll" , - obj, VS ...

This works well on solutions that you control. We have been doing this for many years. And it is very easy to understand if something goes off track, then you are just looking for an assembly with Copy Local = true or Specific Version = True that happens once in a while (forget, get tired, etc.). My current problem is that I do not control the structure or settings of the solution I'm working on, and therefore I am looking for a solution to this ancient problem. I was hoping the VS team would solve this ... Alas ... Team, stop this pain.

0
source

More articles:


All Articles