We have remote developers working on VFP and VS2005 projects. They use their own PC's and connect to our network via VPN (we use the VPN in SBS2003). We use Visual SourceSafe 2005 for all projects. Generally they set up test databases on their PCs (all our databases are SQL 2005) for most of their development and testing, and they can point at our network SQL server when they want to run against real data (again - over the VPN). this way, most of their work is done on their local machine (faster response time).

Our VPN isn't very fast (limited connection options out here in the middle of nowhere) but this setup works pretty well.

Do you really need your developers to operate machines on your network via remote control? To me, that adds complexity and slows things down in general (although it is vertainly doable).

Through some port and port forwarding changes you can use Remote Desktop from multiple remotes to multiple machines on a network. (SBS2003 has Remote Web Workplace which make that a piece of cake). Remote Desktop is my preference for remote access - fast, stable, and built-in!



>We are planning a ASP.Net project soon that will have 1-2 developers working full time from remote sites. We are looking for advice on how to make this work.
>
>We were thinking about setting up a development PC for each remote developer and having them connect to one of these PCs with their own network account. VS.Net would be installed on each development PC. The source would be kept on the network server.
>
>What would be the best, most economical remote access software to allow the remote user to access these development PCs? I have heard of GoToMyPC, but there is also Remote Desktop, VNC, etc...
>
>Also, would anyone recommend Visual SourceSafe? Is there anything better.
>
>Any advice or links to articles would be appreciated.
>
>Thanks,
>
>Jerry