Question about multiple solution files in root

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

Moderator: SourceGear

Post Reply
evolved
Posts: 1
Joined: Tue Feb 06, 2007 11:57 am

Question about multiple solution files in root

Post by evolved » Tue Feb 06, 2007 12:04 pm

Hey guys, I had a quick question for you. I've been up and running with vault for a while now, its been just great. So I'm not a complete noob, I'll just cut to the chase.

I have a repository for a very large solution file. The solution file iteself is bound to the root of a repository, and other projects are nested inside subfolders grouped by use (ie: Workflow folder with a few workflow projects nested in sub sub folders)

Thats dandy, it works great. Now, one of these projects is a web site project from VS2K5. The solution is awesome, but it's kind of a pain in the butt to compile the whole thing everytime i make a small change to the UI in the website. I know theres settings in vs to only compile dependencies, and i know if those projects haven't changed they dont compile, but there are a LOT of them.

How can i make a new solution file which uses my current working folder for the website and a few helper projects and also put that in the root. When you add a solution from sourcegear will it let them pick which solution to use? Whats the best way to go forward with this.

Basically i want 2 solution in the root. One for the heavy coders with all of the projects inside, the meaty stuff that doesnt change very often, and alternatively a lightweight website (and a few small projects that a are helpers)?

All help appreciated, thanks in advance.

.jake

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Tue Feb 06, 2007 4:26 pm

You may be able to create a new solution then and add in each item (project or solution) you need from source control in the layout you want and then use Visual Studio to save it to where you want, then add this to Vault.

Or you could just make a blank solution, and Add it to source control, at the same level as the other solution(s) and then add the projects in from source control that need to be there.

Visual Studio may want to create a new working folder and duplicate the files, rather than use the files from the existing project.

Post Reply