Source control recommendations
I need a good source control application to use with Visual Studio 2008.
I need to be able to check in and out,and view history, compare etc.
I only need it for one developer, so I don't need a $500 application. Something cheaper or free.
Ability to install it on the same box I am developing. Don't need a big ol' source code server or anything.
Plus easy to install and understand.
I need to be able to check in and out,and view history, compare etc.
I only need it for one developer, so I don't need a $500 application. Something cheaper or free.
Ability to install it on the same box I am developing. Don't need a big ol' source code server or anything.
Plus easy to install and understand.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
kukno
BTW: You can install the server on your development PC too ...
ASKER
Kukno,
Thanks. You dont' have to answer this, but if it is convenient and you know...
I know I didn't ask this, but if I install it so that I can develop on my laptop and my pc and get the latest from either box, what is the typical situation for installing the server?
Does source control have to be on the same network, or can it go out over the internet.
Where do most people install the server version? Right on their web servers? or on a separate machine?
If I put it on my win 2008 web server, is that typical? And can it be access remotely, considering my dev boxes are not on the same network?
thanks.
Thanks. You dont' have to answer this, but if it is convenient and you know...
I know I didn't ask this, but if I install it so that I can develop on my laptop and my pc and get the latest from either box, what is the typical situation for installing the server?
Does source control have to be on the same network, or can it go out over the internet.
Where do most people install the server version? Right on their web servers? or on a separate machine?
If I put it on my win 2008 web server, is that typical? And can it be access remotely, considering my dev boxes are not on the same network?
thanks.
ASKER
Hmmm. I notice I also have to have tortoise installed.
> know I didn't ask this, but if I install it so that I can develop on my laptop and
>my pc and get the latest from either box, what is the typical situation for installing
>the server?
on the machine that is up most of the time, so you can access the SVN server from
both. BTW: You need access to the SVN server only if you do "upload" (check in / update)
or "download" (check out) data. Otherwise you will just work with a local copy of the
files.
>Does source control have to be on the same network, or can it go out over the internet.
It uses TCP, so it can be installed anywhere you have access to.
>Where do most people install the server version? Right on their web servers?
>or on a separate machine?
Well, that depends on the team. A lot of open source team do have their SVN server
on the web server of the project.
>If I put it on my win 2008 web server, is that typical?
Well, as I said, it depends on the team what's "typical".
>And can it be access remotely, considering my dev boxes are not on the same network?
Yes, no problem at all.
Cheers
Kurt
>my pc and get the latest from either box, what is the typical situation for installing
>the server?
on the machine that is up most of the time, so you can access the SVN server from
both. BTW: You need access to the SVN server only if you do "upload" (check in / update)
or "download" (check out) data. Otherwise you will just work with a local copy of the
files.
>Does source control have to be on the same network, or can it go out over the internet.
It uses TCP, so it can be installed anywhere you have access to.
>Where do most people install the server version? Right on their web servers?
>or on a separate machine?
Well, that depends on the team. A lot of open source team do have their SVN server
on the web server of the project.
>If I put it on my win 2008 web server, is that typical?
Well, as I said, it depends on the team what's "typical".
>And can it be access remotely, considering my dev boxes are not on the same network?
Yes, no problem at all.
Cheers
Kurt