Sharepoint 2007 as version control

  • Thread starter Thread starter Wenlei Fang
  • Start date Start date
W

Wenlei Fang

Hi All,

Sharepoint 2007 has version control capability, what's your take on using it
as the main version control software for a .Net project of about 1 million
LOC? Is anyone use it for development version control system?

Thanks,

Wenlei
 
It wouldn't be my first choice... give me svn (heck, even vss) any
day; I suspect (without any qualifyication) that it is very document
centric - but code changes tend to be wider than a single document.
I'd also worry about merging, branching, complex rollbacks, etc.
Toolkit support (IDE and/or shell integration) would be a "biggie" for
me (be it the inbuilt IDE offering or things like Tortoise, Ankh,
etc). Anything that makes my job easier.

Can you build system get (the correct version of) the files?

There is also the question of a tin-opener-in-a-tin : i.e. are you
also doing sharepoint development on the same server? If your code
breaks sharepoint, can you fix it?

But I guess it really comes down to: what do you want from your
version control system? If it does whay you mean, go for it! I don't
expect to try any time soon, but if you find it fantastic, please let
me know.

Marc
 
Thanks, Marc.

I'm happy with Totoise SVN/Subversion which we currently are using. It is
suggested by someone (guess who) SharePoint 2007 can be our version control
system for our development team. Just check with the rest of the gang before
I reply "what'd you say".

Best Regards,

Wenlei
 
Wenlei,

If you are going to look at Microsoft Solutions for source control,
Sharepoint would definitely not be my first choice. Rather, you should be
looking at Team System, which offers source control, but also, much, much
more in terms of the tools that are integrated into the suite which can help
greatly (for example, run builds and unit tests when source is checked in,
reject checkins if they fail, etc, etc).
 
While it would give you fair versioning, auditing and granular security to
the code base elements of your project, tied with its in-built task
allocation to help actually run the deliverable, the complexities of having
to maintain what is in effect a collaboration system tightly tied to Office,
not Visual Studio would certainly push me to another tool for source
control. The alerts on code base changes would certainly be interesting
however, as would its ability to accept code via email direct to a
repository.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
 
Back
Top