We have a solution under source control with some file references to custom assemblies (dll's). The file references are compiled dll's we maintain outside of the solution (custom data access dll's similar to the Microsoft Enterprise Library Data Access). The dll's are in a folder named lib under one of the projects in the solution. File hierarchy looks like this:
Solution
Project
lib
DataAccess.dll
The code for the DataAccess.dll is in a separate project maintained outside this solution. Anytime one of my developers needs to make changes DataAccess, when they finish with their changes, they:
Make a fresh build of DataAccess.dll
Check out the DataAccess.dll from the solution referenced above
Copy the new version of DataAccess.dll into the lib folder referenced above
Check in the new version of the dll.
This works fine for the developer making the change, but the new version doesn't get copied down to anyone elses lib folder. To do this, we have to fire up the client tool, highlight the dll, choose get latest and then change the setting to Overwrite existing. Is there some way we can set SourceGear to do this (overwrite instead of merge) when we request a Get all changes recursive from within Visual Studio?
Overwrite instead of merge
Moderator: SourceGear
-
- Posts: 24
- Joined: Tue Aug 01, 2006 2:18 pm
- Contact:
In the Vault Client you can change the Get behavior in Tools - Options - Local Files. Change Modified Working Copy to Overwrite.
If you are using the command line, you can use the switch -merge [automatic|later|overwrite]. See the documentation on the command-line client for more information: http://download.sourcegear.com/misc/vau ... nt/clc.htm
If you are using the command line, you can use the switch -merge [automatic|later|overwrite]. See the documentation on the command-line client for more information: http://download.sourcegear.com/misc/vau ... nt/clc.htm