View Single Post
  #6  
Old 06-29-2007, 09:03 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,003
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