Compatibility path and log dependencies questions

[ambalboa]

First of all, what does the 'Update compatibility directory' do? I mean, it updates the compatibility path, but what is the compatibility path? What is the significance of this?

I also checked the 'Log references found within project group' option in the Project tab, but it didn't log any of the references to other projects. The References... option in the Project menu shows all the project references in VB6 for the project. It builds successfully, but why doesn't VBP log the references on the Output pane?

[kinook]

Originally posted by ambalboa
First of all, what does the 'Update compatibility directory' do? I mean, it updates the compatibility path, but what is the compatibility path? What is the significance of this?

http://www.kinook.com/Forum/showthread.php?threadid=57
http://www.developerfusion.co.uk/show/2164/

I also checked the 'Log references found within project group' option in the Project tab, but it didn't log any of the references to other projects. The References... option in the Project menu shows all the project references in VB6 for the project. It builds successfully, but why doesn't VBP log the references on the Output pane?

Did you build a group (.vbg) from the Make VB6 action? 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 .vbg file and .vbp files (no source code files)

Thanks.

[ambalboa]

No, I did not build a group (.vbg) file using 'Make VB6' action, but a .vbp file. Is that the reason? The EXE file I am compiling in VB6 is a Standard EXE, not an Active EXE.

[kinook]

Well, since the option is

"Log references found within project group: If checked, when building a project group, each project's references to other projects in the group will be logged."
http://www.visualbuild.com/Manual/makevb6projecttab.htm

if you don't build a project group...