:) So a possible solution may be to go TFS or SVN for source and access that over HTTP (although I would have to work around not having one of them for a few weeks). The development itself would be local including testing against SQL Server and local IIS. That would work ok because the web site I will be working on is self contained and I will be the only one working on it. If I can get them to put the test web box in the DMZ (maybe restrict by IP) then I could publish new versions directly to the server and then test the pages against the *real* test database. I am starting to feel a bit more *comfortable* with the idea, thanks. And if it all works smoothly I can spend more time on the beach!!

I guess it would probably be a nightmare working on the source remotely. Flipping between apps; VStudio, SQL server logging on to internal servers etc. Hmmm...what started out as a good idea is rapidly giving me the 'heebie jeebies'

Woops. Ah PVCS, that takes me back a bit.

Funnily enough that's the preferred solution for my fellow contractor. Any ideas on performance over HTTP?

Good point, they are looking to change their source control so would be worth me talking to them about it.

The company are quite new to development, so VSS was the no-brainer for starting up. They are now talking about getting a better solution, not sure if it will be TFS though. Another contractor there would prefer a non MS solution so that' open right now.

Thanks I will take a look at logmein. Not sure if the company would go for it, but I think they are quite open at the moment.

"TFS is great over HTTP though" Really...?

Thats the kind of response time I was expecting. The pages will all be relatively simple, no intense graphics etc. but I might lose it if I have to wait 5 secs everytime I press a key....

Good point. I was thinking that maybe I could just login remotely to lock the source and copy it (although that may end up being a pain when I need to change lots of existing code). Then I could set up my own source control locally and work against a local copy of the SQL Server DB.

I was thinking along the same lines. There are other developers in the office so we would continue sharing common code (although they are developing Win Apps and I would be developing Web). If I work locally, the main problem will be source control (they still use VSS...) followed by publishing changes for testing. I can set up everything I need environment-wise before I go. Design questions may be a bit of an issue because of the time difference. It may be a case of "suck it and see" for a couple of weeks.

Hi, This is the first time I have posted a question and I couldn't find a forum that I thought was relevant to it, other than here. I am a contract software developer currently located in the UK but moving to Melbourne in 2 weeks. A previous client has asked me if I could work remotely in Australia, connecting to a machine in their UK office, to continue developing software for them (.NET Web/Win SQL etc.). I know that technically it is quite straight forward, I have worked remotely in the UK before (VPN) to a local office. However, I am investigating whether or not this is feasible from the point of view of response times, because I would be working intensively and therefore sending many key strokes and expecting a rapid response from Oz <=> UK. Do you have any information that may help me decide whether or not the proposal is workable?