Question with how Vault works

[Caverman]

I'm just curious to understand how Vault is going to integrate with my development scenario.

I want to integrate Vault into VS. I've turned on the option in the Vault Client to do this. Now I'm about to add my project into source control.

I don't have any shadow folders setup just yet but plan to do that as soon as I can get the Net Admin to set me up a User for the service.

My question is that once I add the project to source control and then I check out a file will it save to a working folder? Will the working folder be c:\inetpub\wwwroot\sitename? If not, how will I be able to compile and view the site locally for development?

Until I get Shadow folders working, I'll need to manually move my files out to the Stagging and Production server. If the file that I check in is stored in SQL, how will I be able to copy the files out to my Stagging & Production server?

David

[dan]

My question is that once I add the project to source control and then I check out a file will it save to a working folder? Will the working folder be c:\inetpub\wwwroot\sitename? If not, how will I be able to compile and view the site locally for development?

Visual Studio should set up the working folder as a virtual folder within IIS, so when you make edits, your local web site will have the changes reflected in them. It would be under wwwroot by default, but you can also create a virtual folder to have the working folder be somewhere else too.

Until I get Shadow folders working, I'll need to manually move my files out to the Stagging and Production server. If the file that I check in is stored in SQL, how will I be able to copy the files out to my Stagging & Production server?

Yes, until Shadow Folders is configured, you would have to either copy the files from your local host to a staging server, or install a Vault client and do a Get from the Staging or Production server itself to pull the files down.