OT-develing on several machines

30 Oct 2006 2:44 PM

Jon Doe

Hi

Sorry for this OT post.
What is the norm when you have to use 2 or more machines when you develop? I
use a workstation as my main developer machines, but quite often I need to
use my laptop instead for variouse reasons. How does people tend to handle
the issue with saving y our source code. I guess that I could use sourcesafe
on my fileserver, but what do people normally do? Save projects to a
fileshare or do you store files locally and move it between machines?

/JD

30 Oct 2006 4:18 PM

Neil B

Jon Doe wrote:

> Hi
>
> Sorry for this OT post.
> What is the norm when you have to use 2 or more machines when you
> develop? I use a workstation as my main developer machines, but quite
> often I need to use my laptop instead for variouse reasons. How does
> people tend to handle the issue with saving y our source code. I guess
> that I could use sourcesafe on my fileserver, but what do people
> normally do? Save projects to a fileshare or do you store files locally
> and move it between machines?
>
> /JD

Source control is an invaluable tool for developing on multiple PC's. Do
your work on PC A, commit your code, check-out to PC B, carry on.

I happen to use CVS, but you might prefer SourceSafe, Subversion, or others.

Neil B

30 Oct 2006 4:51 PM

Carl Daniel [VC++ MVP]

"Jon Doe" <JD@nospam.org> wrote in message
news:7ADEEF47-E1A3-48B6-9871-EB9E6FB8CEE0@microsoft.com...
> Hi
>
> Sorry for this OT post.
> What is the norm when you have to use 2 or more machines when you develop?
> I use a workstation as my main developer machines, but quite often I need
> to use my laptop instead for variouse reasons. How does people tend to
> handle the issue with saving y our source code. I guess that I could use
> sourcesafe on my fileserver, but what do people normally do? Save projects
> to a fileshare or do you store files locally and move it between machines?

Absolutely do use source control - even if you're only using a single
machine! I happen to use Visual Studio Team System, but you could use
Source Safe or SourceGear Vault or CVS or SVN or Perforce or ...

Many source control vendors have licenses that permit use by a single
developer for free, even if the product is otherwise commercial (e.g. Vault,
Perforce). Of course, the open-source tools are always free, but in my
experience have inferior integration with Visual Studio - if that matters to
you.

-cd