I am somewhat responsible for a common code base at work. It becomes very frustrating pushing out updates to the libraries simply because people don’t keep track of that stuff or when old projects need updates, a lot of the times it contains the old DLL and the person in charge of changes doesn’t include the latest version. The result ends up being that our code base is fragmented with new/old versions. I want to MAKE SURE that when a project is worked on, it is using the lastest DLLs.
Is there a way in visual studio to set the DLL to import every time? I noticed that once the DLL is in place, even if you update the DLL file, you have to reimport to get the lastest goodies. Is there a way for maybe Visual Studio to reimport it on every start? The DLL will sit on a shared drive, so when I push out new updates I can simply update the DLL on the shared drive and it gives everyone the lastest version automatically.
Even if this is possible, people would have to restart their visual studio to get the updated driver. I tend to leave my workspaces and projects open for days. So it would not help if I were in your office.
Sounds better to me to implement a version control system (ie SVN) and either commit the DLL or the code itself and let people update/recompile as they want. Usually people learn to update and commit often to avoid complicated merge conflicts.
Or do you already have your code under version control?