Building a Project

[ogri]

Hi

We have a fair size project with about 20 dlls related to it.

A guy wrote a small program to go through the entire project and compile it all up, passing it to the package and deployment wizard.

Generally this works fine

However quite often when we pass it through a routine to get the dependencies for all the modules it complains that the one of the source files is newer than the executable that goes with it. If you look in explorer both the .vbp file and the .dll file have the same date and.

The routine that seems to be complaining is pdcmdln.exe, which is the package and deployment command line interface. The way it is executed is to build a small .bat file and execute pdcmdln from within that, passing it as parameters the .vbp source name and where the compiled result should be placed, to generate the dependency files

I cannot see why it is complaining. If I execute pcmdln.exe without parameters it works through panels and will also complain about this module, but at least then gives me the option of recompiling

Has anyone else come across this problem, or knows of any parameters that can be passed to pdcmdln.exe from the command line?

All the best

Keith

 

[ogri]

Hi

Found the problem. Having turned off the autoincrement of the version numbers in the DLLs I no longer have the problem

All the best

Keith