Kinook Software Forums

Go Back   Kinook Software Forums > Visual Build Professional > [VBP] Third Party Tools

Reply
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
  #1  
Old 06-25-2007, 02:58 PM
ambalboa ambalboa is online now
Registered User
 
Join Date: 06-25-2007
Location: Houston, TX
Posts: 70
vb6 project compatibility question?

Hello.

I am trying to build a vb6 project, in which I can set the version number to a specific value, while having the option "project compatibility" selected, which is found on the compatibility tab. However, every time I run it, the step always fails. Now, when I select the "don't change" option, it creates the executable files, and the version number is set successfully. Actually, the other option updates the version number also, but the executible files are not created because it fails.

Maybe someone can help me understand that this option does so that I can avoid this problem.

The error states "Unable to set the version compatible component," "One or more of the properties in 'PROJECT_PATH.vbp' was bad. Some or all of the properties might not be set correctly."

I don't know much about Visual Build Pro. I would really appreciate anyone's help.

Thank you.
Reply With Quote
  #2  
Old 06-25-2007, 03:10 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,750
http://www.visualbuild.com/Manual/ma...ibilitytab.htm

Please ZIP and send or post:
1) The info from Help | About | Install Info
2) The .bld file
3) A build log file
4) The .vbp file (no source code files)

Thanks.
Reply With Quote
  #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
  #4  
Old 06-25-2007, 05:45 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,750
Quote:
Originally posted by ambalboa
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?
Well, it means that the compatibility setting for the project will not be changed and it will be built with the compatibility settings currently configured in the project. See here for recommendations on handling the compatibility setting:
http://www.kinook.com/Forum/showthread.php?threadid=57

Quote:
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

I'm using a 30-day trial version, would that or this particular version be the cause?
No.
Reply With Quote
  #5  
Old 06-29-2007, 08:51 AM
ambalboa ambalboa is online now
Registered User
 
Join Date: 06-25-2007
Location: Houston, TX
Posts: 70
So, the 'Don't change' option means that the GUIDs will not be regenerated? Is that what that means? Also, the 'Binary compatibility' setting, if set, would that cause a conflict with the 'Don't change' option? My goal is to not regenerate the GUIDs, hoping that this help me avoid any reference problems in the future.
Reply With Quote
  #6  
Old 06-29-2007, 09:03 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,750
Quote:
Originally posted by ambalboa
So, the 'Don't change' option means that the GUIDs will not be regenerated? Is that what that means? Also, the 'Binary compatibility' setting, if set, would that cause a conflict with the 'Don't change' option? My goal is to not regenerate the GUIDs, hoping that this help me avoid any reference problems in the future.
Again, the 'Don't change' option in the Make VB6 action means that the compatibility setting for the project will not be changed by the action and it will be built with the compatibility settings currently configured in the VB6 project. If the VB6 project is configured for Binary compatibility, the GUIDs will not be changed by VB6 when compiling. If the project is configured for Project or No compatibility, VB6 will generate new GUIDs (less for Project than for No).

To ensure that VB6 doesn't change GUIDs, set all projects to binary compatibility in the IDE after building the first time or check the 'Set projects to binary compatibility after building' checkbox in the Make VB6 action. See http://www.kinook.com/Forum/showthread.php?threadid=57 for more details on dealing with VB6 and GUIDs.
Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 05:43 AM.


Copyright 1999-2019 Kinook Software, Inc.