Kinook Software Forums

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

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 04-26-2004, 10:26 AM
gmichaud gmichaud is online now
Registered User
 
Join Date: 04-22-2004
Posts: 7
'No Compatibility' option

Why isn't there a "Set No Compatibility" option in the "Make VB6" action? The documentation mentions that project set to no compatibility are compiled and references are updated automatically. We'd like to use this mode instead of project compatibility.

Why? We've found a problem with VBControlExtender and UserControls. As soon as the TypeLib version hits 10, VBControlExtender no longer receive any events. I can't locate a knowledge base article that documents the problem, however there are many posts on Google Groups and most people suggest to rebuild with no compatibility. Also, this post specifically mention that the problem start occuring when the TypeLib version is >= 10, and that's exactly our problem.

http://groups.google.com/groups?q=Wi...ftngp09&rnum=1

The only solution we have is to manually set them to no compatibility, however i'd like to have Visual Build set all of them to "Binary Compatibility" afterwards, like I can do right now when building with "Project Compatibility"

Thanks again!
Reply With Quote
  #2  
Old 04-26-2004, 11:14 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,654
I guess we weren't aware there would ever actually be a need to use no compatibility over project compatibility, or maybe we assumed that anyone doing really advanced stuff would use the typelib method as mentioned in the FAQ to take compatibility issues out of VB's hands.

Anyway, that capability is not currently exposed in the Make VB6 action, and we'll consider adding it for a future release. What you can do for now is use the VSMake tool, which pre-dates the Make VB6 action but does actually have a /nocompat flag to set projects to no compatibility. Add a Run Program step with a command of

%VSMAKE% "drive:\path\to\file.vbg" /nobuild /nocompat

before the Make VB6 action (it is not advised to use VSMake to build as several bugs and enhancements have been fixed/added in the Make VB6 action since VSMake was last updated).
Reply With Quote
  #3  
Old 04-26-2004, 11:19 AM
gmichaud gmichaud is online now
Registered User
 
Join Date: 04-22-2004
Posts: 7
Thank you for your fast reply. This upgrade was well worth the price!
Reply With Quote
  #4  
Old 04-26-2004, 04:21 PM
gmichaud gmichaud is online now
Registered User
 
Join Date: 04-22-2004
Posts: 7
By the way, does this mean that the incremental builds will not work? If the VSMAKE action updates all the project file, the Make VB6 will detect a change and rebuild all the projects, right?

If there's no way to avoid this, I would really like the "No Compatibility" option in a future update of Visual Build.

Thank you.
Reply With Quote
  #5  
Old 04-26-2004, 04:50 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,654
VSMake (like the Make VB6 action) retains the original VBP timestamp when updating the compatibility flag.
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 11:12 PM.


Copyright 1999-2019 Kinook Software, Inc.