.net - How to stop visual studio from updating assembly references? -


in our environment have lib folder contains various third party assemblies referenced our projects. example, enterprise libary , elmah.

sometimes dev doesn't latest on folder. when dev loads project can't find assembly in expected folder, visual studio automatically locates copy , updates project references.

the problem occurs when dev checks in project , screws else up.

is there way stop visual studio 2008 doing this?

update: wanted add using tfs source control.

here's how guard against @ company. (your mileage vary!)

any non-system (or otherwise non-gac) references come our dev server, every developer has mapped w: drive. have common dll directory, subdirectories client (or vendor), , further subdirectories appropriate. no dlls ever stored in source control, except license.dll needed infragistics occasionally.

for vendor-provided libraries (entlib, infragistics, etc.), policy reference w: drive. period. no 1 authorized reference anywhere else. codes hint in project files common path.

for in-house libraries (client , internal projects), our continuous integration process outputs dlls appropriate branch of directory -- again, our references come from.

this slow down our local compile time (for local debugging), vs auto-refresh these against server every time. it's annoyance (sometimes project may take 5 or 6 minutes build locally), it's necessary evil work around people using different references. advantage here checks in code 1 of references, ci server kicks off build , gets pretty darned quickly.

the trick stable, repeatable build process , continuous integration server. we're using cruisecontrol.net, integrated nant builds, insert favorite ci server , build tool here.

so far we've had 0 issues result of process, except when build server kicks in while our source control system (also known demon spawn, see many of recent remarks) performs large multi-file check-in. (as demon spawn doesn't support transacted check-ins.) however, rare occurrence -- perhaps once every 5 or 6 weeks. , force rebuild afterward takes care of it.

just thoughts ... technique should keep people screwing source control -- , added bonus, reduce size of source control won't checking in dlls, dll.refresh files.


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -