How to develop two versions of the same code in VB6

Experts, advice please

I have a fairly complex VB6 project in use by clients.  I need to have the rolled-out version of the code ready always for bug fixes and minor updates.

For development of and experimenting with new functionality, I want to be able to work on a parallel and wholly independent version of the rolled-out code.

What's the best way to organize the projects so that I can work on, run, and create MSI files for two completely independent versions of the same code, please?

Gordon
Gordon_AtherleyAsked:
Who is Participating?
 
SCDMETAConnect With a Mentor Commented:
We use Source Safe as a code repository, but it does not solve the problem of version conflicts.  The biggest problem we have found is when our project has external dependencies that get updated.  

For example, for version 2 of your project you installed the upgrade to version 2 of the COOLBUTTON control.  If you need to revert to your previous version you also need to revert to version 1 of the COOLBUTTON.  It can be a real mess if you have a lot of dependancies.

Our solution: We dedicate one machine as a "Build Machine".  All "release" compiles are performed on this box.
We use DriveImage to create and restore drive images made from the disk.

To make a cut, I restore my previous build image, update the OS with the latest patches, update my dependancies, copy on the new source, compile the code, and build the install. Once the release version is cut, I create a new drive image with the new changes.  I never overwrite an existing image.

Your development box is free to be used for new development.  If you need to hunt down and fix a bug in a previous version, restore that versions drive image and do the fixing on the build machine.  After cutting the patch, create a new image for the patched version.  Carry the bug fixes over to the development machine and incorporate the changes.



0
 
Éric MoreauSenior .Net ConsultantCommented:
I think that your best bet is to use Visual Source Safe and "pin" your version when you distribute one to client. You can then roll back changes if required (for bug fixes and minor updates).
0
 
anvCommented:
best would be to create a separate DLL or component for the new functionlaity that u want to add...

reference the functions etc..that create in it when u want to use the new functionality else use the older functions..

0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
sgayatriCommented:
I normally maintain versions in different folders on the same drive of my machine.
If it is abc60 running on fields, then I shall be working on abc61.
My folders go like this

abcversions (Mainfolder)
abc5x (child of Mainfolder)
  --abc5x_versions.txt
  -- abc50 (subfolders)
  --abc51
  .
  .
  .
abc6x (child of Mainfolder)
  --abc6x_versions.txt
  -- abc60
  -- abc61
so on

And abc5x_versions.txt contains entire version details of all the subfolders of abc5x

0
 
morchubooCommented:
I use CVS myself, whenever you want to release a version to the user, trunk the code tree in cvs and give that - enabling you to carry on coding the main branch.
CVS is completely free to use in any environment and if you visit:

www.pushok.com/soft_cvs.php

They have a CVS proxy add-in for VB so you can submit your work to the CVS repository whever you go home at night.

Hope it helps
0
 
Gordon_AtherleyAuthor Commented:
Points to SCDMETA and thanks to all

I have experienced many problems with version conflicts with dependencies. So SCDMETA's solution serves as a warning as well as a solution.

Much appreciated

Gordon
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.