I have 2 repositories that I want to keep.
1. web project
2. class library .dll
In my web project I simply added my .dll library project to the same solution, but when I try and add it to Vault it adds both the web project AND the class library to the same repository, it doesn't give me the option to choose to seperate them.
how should i go about htis?
best way to setup 2 repositories and my vs.net 2003 solution
Moderator: SourceGear
Also...
Trust me, this isn't a good idea anyway. That's what I thought I wanted to do when I first used Vault (way back in 1.0), but it would have been a disaster.
You want to keep track of all related items in a single repository - your web dll and your class project are both part of your overall application - as is any third party components, documentation, etc. You may want to do branching and merging to support parallel development, for instance, which would break quite badly in a multi-repository solution.
Right now, I have two repositories - one if for a product that we have, and the other is for a completely new product that we're developing. I think (correct me SourceGear if I'm wrong), this is best practices in any source control system.
You want to keep track of all related items in a single repository - your web dll and your class project are both part of your overall application - as is any third party components, documentation, etc. You may want to do branching and merging to support parallel development, for instance, which would break quite badly in a multi-repository solution.
Right now, I have two repositories - one if for a product that we have, and the other is for a completely new product that we're developing. I think (correct me SourceGear if I'm wrong), this is best practices in any source control system.
andrew00's analysis is correct.
Within any given software development project there is invisible cohesion which binds all these source files
together. Keeping these files grouped together allows them to mature and evolve into the next
development effort (branches, labels, snapshots, etc).
For this reason alone, I would always recommend to keep files grouped in the same repository. And, if you
do have separate repositories and you need to consolidate or move objects from repository to repository, then look to Vault 3.5.
Within any given software development project there is invisible cohesion which binds all these source files
together. Keeping these files grouped together allows them to mature and evolve into the next
development effort (branches, labels, snapshots, etc).
For this reason alone, I would always recommend to keep files grouped in the same repository. And, if you
do have separate repositories and you need to consolidate or move objects from repository to repository, then look to Vault 3.5.
Jeff Clausius
SourceGear
SourceGear
VaultNoob,
We do the similar things, because our library (dlls) is maintained by a separate team and used by different projects in different repositories.
The key in Visual Studio is to use dll referencing, not project referencing. To do this properly you have to use a working directory convention that all developers must follow so the dlls are always in the same directory structure relative to a project.
Then you would have one solution for the dlls, and another solution for the web project only, each pointing to its correct repository.
We do the similar things, because our library (dlls) is maintained by a separate team and used by different projects in different repositories.
The key in Visual Studio is to use dll referencing, not project referencing. To do this properly you have to use a working directory convention that all developers must follow so the dlls are always in the same directory structure relative to a project.
Then you would have one solution for the dlls, and another solution for the web project only, each pointing to its correct repository.