William,

>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).

No, we are open to anything. We have no experience working with developers at remote locations and are looking for the best way to handle this.

It makes sense to have the remote developer develop on thier PC for speed concerns. But we would like the source to be maintained in one location, on our network.

In your case, does the developer check out source from Visual Source safe, download the source to thier PC, then check it back in when finished? What happens when one developer checks out serveral things. Can another developer check out one of those modules for testing but not for updating?

Your experiences are appreciated.

Thanks,

Jerry



>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