|
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).
|