Follow up on web projects source control
Just to follow up on a previous post about Source control on web projects over the internet.
After much dinkering around, I basically found no solution that I really liked. I'd tried using a VPN to connect to the server, but it would not work from on campus. On campus, you use a Cisco IP/SEC VPN to get on campus, and the PPTP VPN to my SBS server would connect, but it wouldn't transmit any data. No clue as to why, and I didn't really have the time to look into it, so moved on to another avenue.
Next, I went on to trying WebDAV to map the web site to a local drive. That semi-worked, but I was getting some permission denied errors, plus I didn't really want to enable WebDAV... not the most secure. Next tried FTP, and Visual Studio would load the project, and seemed to recognize the source control, but when I tried to check out/check in stuff, it didn't show up on the Vault server. No clue why.
So I gave up and did what I didn't want to do. All my team members are doing development off of their own machines, and connecting to the database over the internet. I changed the port on SQL Server, but intent on closing that up again as soon as the project is done.
I would like to go back and try to get the VPN working sometime. It would be useful for when I'm on campus and need access to the actual shares on the server. Also, mapping FTP sites to a drive letter is kind of nice. Found a nice free program by Novell called NetDrive. It looks exactly like a commercial one I'd found called WebDrive.
It'd really be nice if in future versions, Vault could support source control with FrontPage Extensions, though it would probably require the web server to be configured for external source control or to have the Vault server installed. SourceGear reading this? Add this! Other than that, Vault is tits.