#1
|
|||
|
|||
Make VB6 Action - Logging
I'm having a problem with the 'Make VB6' action.
I'm build a VB6 group 'vbg' file that has about 30 projects in it. One of the projects called 'QSSGLAcctLookupLaunch.vbp' doesn't get compiled even when files within it's project have changed. It's like VBPro doesn't even see it in the list of projects. VBPro lists all of the other projects and the reason they compiled or no changes. Is there a way to turn logging on or get more logging that shows what exactly VBPro is doing when it determines if a project should compile or not? I also have a side interest in seeing how it is resolving the dependency issues. |
#2
|
|||
|
|||
It should log something for each project in the group.
Please ZIP and send: 1) The info from Help | About | Install Info 2) The .bld file used to build 3) A build log file 4) The .vbg/.vbp files (no source code files) Thanks. |
#3
|
|||
|
|||
I've attached the info in a zip including the html version of the log.
The step with the problem is called 'Build all VB Projects - DELETE PROBLEM DLL's(perpay.dll)' Thanks for the help |
#4
|
|||
|
|||
It does appear to be processing the project QSSGLAcctLookupLaunch.vbp (as much as possible). Looking at the log file, I see that it reports the references it finds in that project. Later on, 3 other projects in the group fail to build. QSSGLAcctLookupLaunch depends on one of those projects (QSSVendorLookup), so it is removed from processing for that step (there's no point in building the dependent project if a project it depends on failed to build). The Make VB6 step only continues building other projects in the group that don't depend on failed projects (if that option is checked, which it is).
|
#5
|
|||
|
|||
Thank you for the help. I should have spotted the dependency issue. Turns out the vendorlookup dependency is new for that launch program and the programmer working on it has been having issues getting it compiled for the last few days. Thanks again for your quick help.
|
|
|