How to rebuild dev server from Vault source???

wchrisjohnson · Post by **wchrisjohnson** » Tue Aug 24, 2004 1:14 pm

Hi,

I have searched the forums/discussions/etc and do not seem to see an answer related to this...

I recently lost my dev server and need to recreate the environment. The dev server (Win2003/IIS) hosted a single web application. Vault is on another server but was used to control the source of this app and it's subprojects. Now, the new server is up and running - Call it SRV-DEV.

Vault is running on a third server dedicated to SCM - Call it SRV-SCM.

I need to develop on my laptop using VS.NET 2003.

How do I recreate what i had before? How do I get the web server (SRV-DEV) to look to the Vault server (SRV-SCM) for its source code initially?

I looked through the MS doc that gives an overview of VSS and web projects, but it always assumed the setup of web projects started with the developer checking in a new project(s) froom within the IDE. I need to reverse that.

Thanks in advance for any direction someone can give. If this has been answered elsewhere, feel free to just point me there.

Chris

dan · Post by **dan** » Tue Aug 24, 2004 2:25 pm

Was SRV-DEV set up as a shadow folder that contained the latest checked in version of the web app, or was the SRV-DEV web server used as a working folder/virtual IIS folder that you checked files from/to while doing development?

Guest · Post by **Guest** » Tue Aug 24, 2004 2:31 pm

Hi Dan,

SRV-DEV was set up as the working folder/virtual IIS folder that I used as the primary source for checkin/checkout. The Vault DB is actually on my laptop; SRV-DEV is actually a W2K3 VM (VMWARE) on my laptop.

I did it this way because I needed to host multiple websites under W2K3 Server and cannot do that on XP (localhost).

Chris

dan · Post by **dan** » Tue Aug 24, 2004 2:40 pm

OK, then I think the best way to go is to start with a fresh working folder on your laptop, and then invoke VS.Net from there, and do an Open From Source Control, and choose the Vault folder that contains the solution/project. It will ask for two working folders - one for the web app and one for everything else. Make sure you use the SRV-DEV folder for the web app, and hopefully it will be the same as before.

wchrisjohnson · Post by **wchrisjohnson** » Wed Aug 25, 2004 8:52 am

Hi Dan,

That doesn't seem to work. Here's what I am seeing:

1) Open VS.NET 2003
2) Click File--> Source Ctrl --> Open From Source Control
3) Choose the appropriate Repository
4) "Create Local Project from Vault" dialog - options:
- Project to open: primary project in Vault (can not set - done automatically)
- Create new project in working folder: physical directory linked to virtual directory on the web server (in the VM)
- Vault folder to download: primary project in Vault

5) "Set Project Location" dialog:
- Project Name: same as Project to open
- Source Control Server Location: <Unable to display>
- Enter Working Location Copy Here: URL of web server working folder

When I hit enter on that last dialog, I get the following error:

"Unable to create web project http://<server name>. The UNC share '\\<server name>\wwwroot$' does not exist or you do not have access."

I am pretty confident I have the appropriate permissions for the web server; maybe not.

I would appreciate GREATLY any additional help you could provide.

dan · Post by **dan** » Wed Aug 25, 2004 9:29 am

It looks like you can't create a virtual folder on another machine via Visual Studio.

Try this: Manually create the virtual folder again on the SRV-DEV machine (make sure it is a new one, and not the old one you were using). Then, when Visual Studio asks for the URL, provide that as the URL, and hopefully it will be able to communicate.

Also, it would probably be best for you to specify a local folder for the first working folder, and not one on the SRV-DEV machine.

One last thing: You'll need to make sure that no one else is using the virtual folder on SRV-DEV as *their* working folder too. Two people cannot share a working folder - it will cause a lot of state problems with the working folders.