An Automatic Build Incrementer for VC6

Environment: Visual C++ 6.0

Visual Basic programmers have long had the ability to automatically increment the build number each time the program was compiled. Visual C++ programmers haven't.

Several weeks ago, I started trying to find a way to do automatically increment build numbers on each compile. I found several articles on the subject and some source code but none of it did exactly what I wanted it to do, so I decided to write my own incrementer.

Add the code to an existing macro file or, if you don't have an existing macro file, create one and add one dummy macro so you can access the code snippet. Application_BeforeBuildStart() is a Visual Studio defined event handler and although the code is in a macro file, when you select the Tools|Macro menu item, you won't see it, so you need at least a dummy macro in the file to access the source code.

Note that these code snippets have been subjected to limited testing and that you use them at your own risk. They work correctly in the test environment, but you assume all risk for their use. I will not assume any liability whatsoever for their failure to work correctly in your environment.

Please e-mail any comments, suggestions for improvement, problems, etc. to me.

Sub Application_BeforeBuildStart()
 ' written 7/11/00 by CCB Consulting
 ' e-mail any comments, corrections, etc. to
 ' updated versions will be at on the Code Snippets page
 ' invoked automatically before build starts
 ' will open the project's *.rc file as text
 ' will search for the version info
 ' and will increment the build number

 dim oDoc
 dim sBuild
 dim sRCFile
 dim sOne
 dim sTwo
 dim iSelect
 dim lLineNbr
 dim bFound

 'get the name of the active project's .rc file
 sRCFile = application.activeproject & ".rc"

 'open *.rc file as text
 set oDoc = Documents.Open(sRCFile, "Text")

 'position to the correct section of the file
 oDoc.Selection.FindText " FILEVERSION", dsMatchCase
 'save the line number for the next search
 lLineNbr = oDoc.Selection.CurrentLine

 'use a regular expression search string for the first version search
 sOne = "[0-9]+,[0-9]+,[0-9]+,"

 'find the first string
 oDoc.Selection.FindText sOne, dsMatchRegExp

 if oDoc.Selection.CurrentLine = lLineNbr then
  'convert the regular expression to an absolute search string
  sOne = oDoc.Selection

  'build an absolute search string for the strings with embedded spaces
  sTwo = Replace(sOne, ",", ", ")

  'move to the build number

  'select the build number
  oDoc.Selection.WordRight dsExtend

  'increment the build number
  sBuild = oDoc.Selection + 1

  'replace the old build number with the new one
  oDoc.Selection = sBuild

  else 'something went wrong
   msgbox "Version number 1 not found. Closing without changes."

   oDoc.Close dsSaveChangesNo

   set oDoc = nothing

   exit sub
 end if

 'now change the other 3 occurences of the build number
 for iSelect = 2 to 4
  if iSelect = 2 then 
   bFound = oDoc.Selection.FindText(sOne)
   bFound = oDoc.Selection.FindText(sTwo)
  end if

  oDoc.Selection.WordRight dsExtend
  oDoc.Selection = sBuild

  if bFound = False then
   msgbox "Version number " & iSelect & " not found. Closing without changes."
   oDoc.Close dsSaveChangesNo
   set oDoc = nothing
   exit sub
  end if

 'close and save *.rc
 oDoc.Close dsSaveChangesYes

 set oDoc = nothing
End Sub


Download source - 2 Kb


Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Anthony Christie, the Chief Marketing Officer for Level Communications, is responsible for customer experience, worldwide marketing and product management. In this informative asset, he shares his insights into why a private network connection to cloud-bases applications is the right decision for your enterprise. Download now to find out more.

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date