J.G. Williams

I used to be able to run VSS from home using our company's VPN without any problems at all - even if it was a bit slow. For some time now, though, it has been appearing to hang with no activity at all. Running FileMon, however, reveals that there is activity. Bear with me while I explain:

In this instance I am using VS2003, but the same thing seems to happen with VS2005 as well. We have a largish solution with multiple projects, two of which are web projects - call them webproj1 and webproj2. I am running VS2003 and clicking on Source Control/Open From Source Control. After a bit the screen goes blank and all activity seems to stop. Using FileMon reveals that Studio is attempting to open the file 'C:\Program Files\Visual Studio.NET 2003\Common7\IDE\http:\localhost\webproj1' and likewise for webproj2. Unsurprisingly the result is 'NAME INVALID'. I have also tried using SourceOffSite, but the result is the same. Can anyone tell me what on earth is going on here, please

Thanks

John Williams.



Re: Visual Studio Source Control and SourceSafe VSS over a VPN connection

Nitin Gupta MSFT

Hi John,

Are you trying to connect through VSS Internet or using VSS Local Also, can you please check if you have the .suo file as part of your solution. It should be present at the same location as your solution file.

Thanks,

Nitin





Re: Visual Studio Source Control and SourceSafe VSS over a VPN connection

J.G. Williams

Hi Nitin

Wow! I'd assumed after all this time that nobody had a clue what was wrong, so thanks for responding.

With regards to VSS Internet or VSS local, I guess it's VSS local. When it used to work fine it was definitely local, as we were all on VSS 6. I haven't managed to isolate exactly what happened when it stopped working. It may have been related to moving to VSS 2005, but I've sinced tried putting back VSS 6 and it still doesn't work. I had noticed that VSS 2005 had an internet option, but I've not investigated it at all. I had assumed that using SOS would fix my problems, so I was a little surprised to find that this exhibited exactly the same problem.

With regard to the .suo file, not this isn't included.

Thanks again for trying to help.

John





Re: Visual Studio Source Control and SourceSafe VSS over a VPN connection

Alin Constantin - MSFT

Hi,

Let's talk about VS2003 case.

In VS2003 there are 2 types of web projects: FrontPage web projects and FileShare web projects.

1) If you have FP webs: the paths used by VS to open the web projects are stored only in the *.sln file. The rest of the web project files are stored on a remote FP server, and the open from source control operation does not affect the FP web project (scc operations like AddToScc/OpenFromScc don't apply for web projects, they are done remotely at the server).

If your projects are FP webs you should checkout the solution file, edit the file with notepad and fix the web project paths, then checkin your changes.

2) If you have File Share web projects: The sln file contains in this case the web project path used by the first user who added the project to scc, and these paths are not used during OpenFromScc. During open from scc you should be prompted with a SetProjectLocation dialog where you can type in new paths for your web project enlistments - file share webs always require new enlistments when opened from scc. (You don't seem to mention seeing this dialog, I wonder why this happens...). Anyway, the paths you type in the SPL dialog (generally like http://localhost/WebProject1_1) are persisted in the *.suo file, and they are used further by the IDE to open the project from this location.

If your projects are file share webs, make sure you're not opening the solution from source control in an existent location (where there may already be a bad suo file). Make sure the suo file was not accidentally added to the VSS database (this file should not be under scc). Verify the paths in the sln file - perhaps the paths there are bad and VS doesn't recognize them as web projects. If everythis else fails, you should remove the bad projects from the solution, then use File/SourceControl/AddProjectsFromSourceControl command, locate the vbproj files in the VSS database, and add these projects to the solution. You should be prompted with the SPL dialog in this case, too, to pick current enlistment for your webs.

In VS2005 the web project types are: FTP (don't support source control), FrontPage (similar to FP in VS2003), LocalHost and LocalDisk (similar to file share in VS2003). For the later project types, the SPL dialog has been removed, and the current enlistment paths are automatically calculated by the web project (generally as subfolders of the solution's folder)

Alin





Re: Visual Studio Source Control and SourceSafe VSS over a VPN connection

Catherine Sea

Hi John,

You can try SourceAnywhere for VSS, which is recommended by Microsoft for SourceSafe remote access.

The web site is:

http://www.dynamsoft.com/Products/SAW_Overview.aspx

Thanks,




Re: Visual Studio Source Control and SourceSafe VSS over a VPN connection

J.G. Williams

Thanks for all your answers, folks. I have no idea what is causing the problem with our VS2003 project, but fortunately this is pretty much a non-issue now, as the next release will be the .Net 2 version.

With regard to the VS2005 project, I did manage to get this to work OK eventually. We have been using SourceOffSite, and this worked OK for the most part but crashed occasionally with some rather strange messages. So I have downloaded and installed SourceAnywhere, and I must say this seems to work far better (thank you Catherine - I'd never heard of it before). So now I shall have to go and talk to the IT manager about his budget!

Regards

John





Re: Visual Studio Source Control and SourceSafe VSS over a VPN connection

Catherine Sea

Hi John,

You are welcome.

I am glad to hear that SourceAnywhere for VSS works great for you.

Thanks.