Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
ASP.NET 2.0 Professional If you are an experienced ASP.NET programmer, this is the forum for your 2.0 questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Professional section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old December 1st, 2010, 07:20 PM
Authorized User
Points: 169, Level: 3
Points: 169, Level: 3 Points: 169, Level: 3 Points: 169, Level: 3
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Apr 2008
Location: Northampton, , United Kingdom.
Posts: 35
Thanks: 1
Thanked 0 Times in 0 Posts
Default Version Control

I am seeing solutions on how best to manage version control of .NET applications (multi developer) inline with components outside of the .NET application; such as web services, databases, etc.,?

For years, our projects have been worked on by one developer at a time - typically they're either straight forward or small solutions that haven't needed more than one developer, so version control is rather well managed by (originally) SourceSafe and (in the past couple of years) SubVersion. We're using Visual Studio 2005 at the moment; migrating to newer versions would be quite a big task.

But, more recently we're team working on a couple of much bigger projects with a couple of UK developers and a small team in our offshore office and whilst we're managing well with SubVersion, it's a bit of a pain for our Release Management (RM) as we need to compile different versions into a release, not so straight forward with a .NET application and SVN.

The development teams for each component use SubVersion successfully, but it's how best to coordinate it all back for a production release that we're struggling with.

I would be interested in hearing of "successful" solutions that others have implemented.

Is it any easier with more recent versions of Visual Studio?

Any advice appreciated.


Last edited by fullingdale; December 17th, 2010 at 10:31 AM.. Reason: Rephrased some of the question

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
How to use CVS version control in Asp.net jagathdworld Visual Studio 2005 3 June 2nd, 2009 01:30 PM
Passwords from version 1 to version 2 Maxxim BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 3 February 6th, 2007 06:49 PM
latest version of MySQL Control Center crmpicco MySQL 2 September 12th, 2005 10:07 AM

All times are GMT -4. The time now is 10:50 AM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.