View Single Post
  #4  
Old 03-30-2006, 07:41 AM
pmcclosk pmcclosk is online now
Registered User
 
Join Date: 01-24-2006
Location: State College, PA
Posts: 7
I've tried a few things since posting this. The problem seems to be in the StampVer.exe tool that came with VBP. The build sets the correct changelist number, today's being 65540. In the output for the StampVer step, the build number is 1004. Here is the command for this step:

%TOOLSDIR%\StampVer "%SOURCE%\our_executable.exe" -p"%VERSION_NUM%.%BUILD_NUM%" -f"%VERSION_NUM%.%BUILD_NUM%"

When hovering over this, the %BUILD_NUM% macro displays 65540, the correct value. The step output is still showing 1004, and that's what the file is ultimately stamped with. A lot of our processes DEPEND on accurate file versioning. This all began on March 1st, is there a known bug in the StampVer.exe? This product is using VBP 5.0. We're too close to release for this particular product to put time into upgrading to a newer version of VBP on this particular machine.
Reply With Quote