Make VB6 and No Compatibility

[ajd]

Hi,

I have one VB project group containing 2 VB6 projects - CompA and CompB.

If CompA is dependent on CompB and both projects have their compatible mode set to 'no compatibility' then should I expect the reference in CompA's project file to CompB to be updated automatically when using the 'Make VB6' action? This does not seem to happening for me. I continually get the 'Can't find project or library' error as CompA can't get the reference to CompB once CompB has been rebuilt.

I do not want to use project or binary compatibility.

I am using VB Pro 5.4

Thanks

[kinook]

Yes, that should work. Attached is a modified version of the VStudio.bld sample that does this (setting the VB projects to no compatibility before building), and it works as expected here when saved in the VisBuildPro\Samples folder and built.

If you can tweak the sample to reproduce the behavior you're seeing, or provide a reproducible case, ZIP it with folders preserved, post it here we can take a look at it. Also see this FAQ for some general recommendations on handling VB builds:
http://www.kinook.com/Forum/showthread.php?threadid=57