What happens to the .dll with multi developers?

Caverman · Post by **Caverman** » Wed Aug 18, 2004 2:46 pm

I just recently setup Vault and I’m still testing it out. So far I’m the only one using it but I’m about to have a second developer start using it.

I’m curious of how this will affect the .dll in the bin directory in the Repository.

If developer 1 checks out a page it will bring a copy down to their local machine so they can build and test the application locally. If developer 2 checks out a different page it will also be copied down to their local machine.

If developer 1 then compiles and checks the page back in then the .dll will have the changes that were made by developer 1. If after developer 1 checks in his page, developer 2 checks in his page, what will happen to the .dll? Will the .dll from developer 2 overwrite the .dll that developer 1 checked in? If so, will there be an error with the changes that developer 1 made because the .dll from developer 2 doesn’t know about the changes developer 1 made?

I’m assuming multiple developers can check out different pages and not really affect the .dll that is stored in the repository?

David

dan · Post by **dan** » Thu Aug 19, 2004 8:56 am

Binary files like dlls are not merged by Vault, their source code file are. So, if developer one modifies a .cs file at the same time as another developer, both sets of changes will be merged into the repository. If a dll is modified at the same time by both developers, their changes won't be merged.

Normally, dlls and other binary files are not checked into the repository as part of normal development process. A lot of people like to put the output of build scripts and official versions under source control, but not dll changes that are part of regular development.