(But Visual Studio 2005 + Source Safe Internet Plugin + Vista = ahhhhhh)
----------------------------------------
UPDATE: I didn't realize that even though everything looks to be set up, your changes to files are not replicated to the web server. Only the source control repository is modified. Back to the drawing board...
So basically, ignore the rest of this post... My bad...
----------------------------------------
Note that this post pertains to remote development where your dev server is remote.
I upgraded to Vista last night to hopefully resolve a problem with VS2005 hanging in XP when trying to add references to dll's. I had hoped that either the new operating system, or the new service pack for Vista would solve my problem. Vista itself is fine. More than fine. At least on my machine. Apps are fast to launch and I think my network connectivity is even a little faster. The problem is if you have websites that you open via front page server extensions. As soon as you try to load one up, wham! "The program Visual Studio 2005 has stopped working" (or something like that). If you view details it will show you APPCRASH for devenv.exe. Great job with the backwards compatibility boys...
If you're not using any source control then the solution is easy: just run an FTP site on that machine and open web site > from ftp.
If you have SourceSafe, your road is a little longer and painful. Well, less painful because hopefully my advice will get you straightened out a lot faster than it took me.
1) Start by removing the frontpage server extensions from your website in IIS. If you add your project to source control, your project will remain in the sourcesafe database and you can "open web site from source control" later in these instructions.
2) You need the ability to open files directly from the sourcesafe database on your remote server. Follow these instructions to get set up. I couldn't get it to work without HTTPS, so I recommend you do so as well.
3) Note that if you have a self-signed certificate that you made with your own homemade certificate authority in windows, you will need to install that certificate on your newly upgraded machine. Even if you did so in the past for XP. Load up your sourcesafe web service URL in IE so you can view the certificate details, and retrieve the certificate for the certificate authority (not the certificate for your web service site, the one for the CA). You should be able to double click the cer file and import it into your Trusted Root Certification Authorities store.
4) You may get a fakakta error code when trying to "open web site > from source control" like 0x80072f19. If you do, launch Internet Explorer and you need to uncheck Check for Server Certificate Revocation under Advanced within Internet Options. Yes, a setting in your browser affects a completely different program. (Well probably these settings are the same as those in the control panel for internet options)
5. So then, if you Open Web Site > From Source Control it will ask you where on your local drive to store the files you check out, make a folder for them, and off you go.