VB6 projects not getting compiled properly from VBP

[saurabh]

I agree with both the points you mentioned:
There will be ifferences in the two DLLs, atleast timestamp difference. And Make VB6 does nothing but call VB6.exe in turn.

BTW, I have not tried/tested running the step group containing only the compile part (i.e group having step 1, 1a and 1b). I have eaither run full build (start to end) or have run only the extra step included to compile a single project.

DLL/OCX produced (from full build) have only run time issues (display not proper).
Do you think there could be some underlying issue which I'm not able to imagine. Only if I know the root cause of the problem will I be able to find a solution for that. I'm stuck bdaly!!

[kinook]

I haven't heard of anything like that before. Could there maybe be some sort of circular dependency between projects that requires a particular build order for everything to work properly?

You might try putting all the projects in a .VBG file (could generate this using the loop you already have and write the filenames out like Project=filename) and building that from a Make VB6 step instead, letting it update references, and see if that makes any difference.