View Single Post
  #3  
Old 06-25-2007, 05:12 PM
ambalboa ambalboa is online now
Registered User
 
Join Date: 06-25-2007
Location: Houston, TX
Posts: 70
Thank you. I checked out the link, but I don't see where it explains the "Don't change" option, to get an idea of why that works for my project. Does that mean that the interface and class GUIDs are not regenerated? And if so, would there be compatibility issues more likely down the line?

For the moment, here is the install info on vbp

Visual Build Professional 6.2
Evaluation Version: 20 days remaining
Windows Version: 5.1.2600.2.0
Install path: C:\Program Files\VisBuildPro6
SftTree_IX86_U_50.dll version 5.05
unins000.exe version 51.42.0.0
VisBuildCmd.exe version 6.2.0.2
VisBuildPro.exe version 6.2.0.2
VisBuildBld.dll version 6.2.0.4
VisBuildBurn.dll version 6.2.0.3
VisBuildCore.dll version 6.2.0.3
VisBuildDotNET.dll version 6.2.0.3
VisBuildExt.dll version 6.2.0.3
VisBuildLog.dll version 6.2.0.2
VisBuildMisc.dll version 6.2.0.3
VisBuildMS.dll version 6.2.0.4
VisBuildMS2.dll version 6.2.0.2
VisBuildNet.dll version 6.2.0.3
VisBuildSvr.dll version 6.2.0.4
VisBuildSvr.Interop.dll version 1.0.0.0

I'm using a 30-day trial version, would that or this particular version be the cause?

I'll see if can send you the rest. Thank you.
Reply With Quote