Sharing Web Projects

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
smercill
Posts: 4
Joined: Wed Mar 23, 2005 11:00 pm

Sharing Web Projects

Post by smercill » Wed Mar 23, 2005 11:21 pm

We are evaluating vault and we are trying to share a single web project between multiple solutions what is the best approach?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Thu Mar 24, 2005 9:46 am

Sharing projects can be tricky.

See if this KB article provides some useful information:
http://support.sourcegear.com/viewtopic.php?t=890
Linda Bauer
SourceGear
Technical Support Manager

smercill
Posts: 4
Joined: Wed Mar 23, 2005 11:00 pm

More info about Sharing Web Projects

Post by smercill » Fri Mar 25, 2005 8:38 am

We are evaluating your Vault product, but we are running into an issue. We have Web application that acts as an application framework. The framework is very similar to DotNetNuke.

We would like to create a core web project in vault share it between multiple solutions. This would allow us to have a team work on the core application and then I can have other development teams working on various customizations. For some reason when we try to share the web project and then try to add it another solution. Vault wants to remove it from the source control and rebind as a new project.

Could you please provide some insight? If you need anymore information please let me know.

gmagana
Posts: 145
Joined: Wed Feb 18, 2004 10:51 am
Location: Santa Ana, CA, USA

Post by gmagana » Fri Mar 25, 2005 6:13 pm

When doing this kind of non-trivial stuff with VS, make sure you understand exactly what is going on... Visual Studio tries to fix things without letting you know, so it does all sorts of dirty tricks to make source control match its world-view.

For starters, make sure that the solution file in the directory tree is above the projects, for some reason VS wants it that way, if it is not, then VS "fixes" the version control structure so that it ends up this way. Somethign VS will create new projects, which on the working folder seems ok, but if you look in the version control it will be actually a duplicate of the original project, and everything will be screwed up.

So follow Linda's link, and read that doc several times, VS can really screw up version control and not even tell you about it.
gabriel magana-gonzalez

Post Reply