0

I have a complex Visual Studio solution working with the data from a database. The database will be modified according to the new business rules, for this reason a new database will be created.

The user needs to work for some years with the old database too. The requirement is to create a new version of the application. Handling the two databases with the same application would be too complex and would create only problems to the users (and to us). The two versions of the application will be installed on the same PCs.

No new funktion will be added to the old version of the application, only bug fixing. Actually I do not see any reason to create a branch. I just want to have on the hand the code of the old version if any bug has to be fixed (any way actually it is a very stable version, without issues since 6 months)

I am just thinking simply to clone the solution folder and create a new product version for the new version. Of course I will take care of all paths and references in the new folder, while the solution consist of many projects and assemblies (more than twenty).

Has this way any drawback or shall I go in any case with a version controlling (svn)? In the past with visual studio 5/6 I was used to clone the project folder for each new major release and it had always worked. Now I have less confidence to do the same with Visual Studio 2010.

Actually I use svn only as backup/recovery system.

Thank you for replying.

gingo
  • 468
  • 1
  • 4
  • 18
  • 2
    //Actually I do not see any reason to create a branch.// Not the way I'd go, or many people would go. This is the exact reason you would create a branch...... – granadaCoder Feb 19 '14 at 17:19
  • 1
    http://vsarbranchingguide.codeplex.com/releases I'd read the "branching and merging guide.pdf".......and get a source control solution. git, tfs, svn.. would be my suggestions (in that order) – granadaCoder Feb 19 '14 at 17:22
  • Sorry, maybe I should write "I do not understand the reason to use a branch". I have not so much experience with branching/Tagging, while I use svn more as backup/recovery system. Thank you for the link. – gingo Feb 19 '14 at 17:40
  • Ok...that makes more sense. Yeah, read the guide.....it should be helpful. I use tfs now at work, but I'd go "git" if I needed a non tfs solution. http://stackoverflow.com/questions/161541/should-i-use-svn-or-git – granadaCoder Feb 19 '14 at 18:41

0 Answers0