OT: Visual Studio with 3 developers and same projekt

[Cowboy \(Gregory A. Beamer\)]

This depends on budget, etc.

With three developers, and a larger budget, you might use Team System. It
has a nice version control system that links into reports and project
management. But, it is awfully expensive if all you are using is version
control. Unless you take full advantage of the designers, test bits, and use
Project for your project management, SharePoint for your Content Management,
it is a lot of money.

If you are not using all of the features of VS Team System, I would go down
to the Visual Studio Professional edition. Standard is just missing too many
features for me to recommend it. In this case, you have a couple of options
for source control.

1. For easy set up, SourceSafe is an option. The latest version(s) allow you
to choose whether or not to exclusively lock files and have a merge module,
making them more flexible. It is still not an Enterprise level source
control. If your libraries are used by other teams, this is not the greatest
option, IMO.

2. For more Enterprise level control, without the TFS cost, there are open
source repositories like CVS and Subversion and pay repositories.

Open Source: Of the two, I have enjoyed Subversion more. This is partially a
familiarity issue, so take my advice here with a grain of salt. On the
project I worked on with CVS, I was not in control of the Repository.

Pay: I am ratehr fond of Source Gear's products. I have worked quite a few
consult gigs who used Vault. Source Gear now has a product called Fortress,
which is also a bug tracker (if you already have one, ignore). Vault (and
Fortress) are easy to set up. The pricing is $249 per developer (Vault) and
$499 per developer (Fortress), so this is not a free option. These products
are easy to set up and start using and work with Visual Studio, including
Visual Studio 2008.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************

 

[Jon Skeet [C# MVP]]

This depends on budget, etc.

With three developers, and a larger budget, you might use Team System. It
has a nice version control system that links into reports and project
management. But, it is awfully expensive if all you are using is version
control. Unless you take full advantage of the designers, test bits, and use
Project for your project management, SharePoint for your Content Management,
it is a lot of money.

Note that you can still use a lot of that by buying the TFS server,
but installed Team Explorer in conjunction with VS Pro. It works
reasonably well - although there are still plenty of features I miss
from svn. (It's definitely a massive improvement over VSS, of
course

Open Source: Of the two, I have enjoyed Subversion more. This is partially a
familiarity issue, so take my advice here with a grain of salt. On the
project I worked on with CVS, I was not in control of the Repository.

I'd *expect* SVN to be a more attractive option than CVS, given that
the whole reason for its existence is to fix the problems with CVS

SVN is one the best thought-out pieces of software I've seen. I know
it's not natively good for distributed repositories (like git is, for
instance - not that I've used git) but for most shops it does the
right thing, and does it *very* well.

Jon

 

[Rad [Visual C# MVP]]

[8 quoted lines suppressed]

Note that you can still use a lot of that by buying the TFS server,
but installed Team Explorer in conjunction with VS Pro. It works
reasonably well - although there are still plenty of features I miss
from svn. (It's definitely a massive improvement over VSS, of
course

[3 quoted lines suppressed]

I'd *expect* SVN to be a more attractive option than CVS, given that
the whole reason for its existence is to fix the problems with CVS

SVN is one the best thought-out pieces of software I've seen. I know
it's not natively good for distributed repositories (like git is, for
instance - not that I've used git) but for most shops it does the
right thing, and does it *very* well.

Jon

Jon, take a look at Mercurial. Been evaluating it for the past few weeks
and it seems pretty robust.

 

[Rad [Visual C# MVP]]

1. For easy set up, SourceSafe is an option. The latest version(s) allow you
to choose whether or not to exclusively lock files and have a merge module,
making them more flexible. It is still not an Enterprise level source
control. If your libraries are used by other teams, this is not the greatest
option, IMO.

I used to use SourceSafe a couple of years back and all I have to show for
it are grey hairs. Mysterious database corruption, files that woulde fuse
to check in/check out, getting the latest versions and discovering 100
miles later that it never actually got the latest versions ... SourceSafe
needs to be weighted and buried at sea

2. For more Enterprise level control, without the TFS cost, there are open
source repositories like CVS and Subversion and pay repositories.

Open Source: Of the two, I have enjoyed Subversion more. This is partially a
familiarity issue, so take my advice here with a grain of salt. On the
project I worked on with CVS, I was not in control of the Repository.

Take subversion any day of the week. This is what I use now. It addresses
many of the problems of CVS, the biggest one being that with CVS if
something happened during a commit you'd be left in a mixed state with some
files committed and some not. In subversion commits are atomic.

You can get good shell integration with TortoiseSVN and visual studio
integration with AnkhSVN or even better, Visual SVN (though that's not
free)

 

[Rad [Visual C# MVP]]

[7 quoted lines suppressed]

Ankh seems to do everything I need, so I haven't tried VisualSVN. I do
admit that for a few things (like diffs) Ankh is relatively primitive.
What are the main benefits in your view of VisualSVN over Ankh?

Maybe I should give VisualSVN a try... only problem is that it means
uninstalling Ankh first. (For some reason unticking the box in the Add-
In manager doesn't actually seem to do much.)

Jon

Having used both, I can say with Authority that I prefer VisualSVN is for a
couple of reasons
- More polished in terms of look and feel
- Integration with TSVN, so TSVN do the hard work. TSVN is very polished
and very mature and the VisuaSVN guys have seen no need to re-invent the
wheel
- Handles renames much better than AnkhSVN
- Pleasantly discovered that it can create a repository complete with the
trunk folder from within a clean visual studio solution. (Though I'm not
sure Ankh can't do this)

 

[Jon Skeet [C# MVP]]

Having used both, I can say with Authority that I prefer VisualSVN is for a
couple of reasons
- More polished in terms of look and feel
- Integration with TSVN, so TSVN do the hard work. TSVN is very polished
and very mature and the VisuaSVN guys have seen no need to re-invent the
wheel
- Handles renames much better than AnkhSVN
- Pleasantly discovered that it can create a repository complete with the
trunk folder from within a clean visual studio solution. (Though I'm not
sure Ankh can't do this)

Righto. Will give it a go

 

[RobinS]

Personally I'd say that anything with Visual SourceSafe is
inappropriate. It's a terrible, terrible source control system.

From http://www.wadhome.org/svn_vs_vss.html (not unbiased, I know):
<quote>
Here's a quote I once heard from someone who works at Microsoft:

"Visual SourceSafe? It would be safer to print out all your code,
run it through a shredder, and set it on fire."
</quote>

I'm happy with the hope that if I'm lucky, I may never need to use VSS
again.

Don't hold back, Jon. Tell us how you really feel! ;-)

I agree, by the way. The day my company decided to go from using VSS to Team
Foundation System (less expensive than the whole Visual Studio Team System)
and VS2008 was one of the best days I've had in the last year. Just doing a
GetLatest went from 15 minutes to 1 minute. And we get to track all of our
work internally in TFS.

RobinS.
GoldMail, Inc.

 

[RobinS]

I always use Pro, Team System is too expensive.
Source Control: Subversion, or Sourcegear Vault if you prefer a commercial
product.

regards, Robert

I agree that VSTS is too expensive. We bought a license for Team Foundation
System and we use that with VS. It gives you a lot of the same functionality
that VSTS, but at a much lower cost. We can track bugs, enhancements, etc.,
get reports, manage our work, and it's all integrated with VS. I've been
really happy with it since we switched over last December.

RobinS.
GoldMail, Inc.

 

[RobinS]

I used to use SourceSafe a couple of years back and all I have to show for
it are grey hairs. Mysterious database corruption, files that woulde fuse
to check in/check out, getting the latest versions and discovering 100
miles later that it never actually got the latest versions ... SourceSafe
needs to be weighted and buried at sea

I think the oceans are polluted enough, don't you? I would only recommend
this method if it were cremated first; then it would just settle to the
bottom as dust. ;-)

RobinS.