cancel
Showing results for 
Search instead for 
Did you mean: 

Powerbuilder EXE/DLL Versioning

Former Member
0 Kudos

Hi,

whilst PB (12.5.2) observes version information entered in "Project - Version Information" tab during compile and build of a full project it does not do so if you just build a runtime library from PBL included in project.

Our objective is to have the possibility to deploy only changed PBL/DLL's as patches due to large project. We often implement minor changes which need to be rolled out to production environment quickly.  Due to the size of our project Compile, Build and MSI gerneration takes at least 2h. Not to mention the  install time in production environment with 100+ clients.

For such minor updates we would like do deploy MSP file to clients. Building the MSP is not a problem, but due to the fact, that PB ignores Version Information when building single runtime library from PBL we must manually edit DLL version info before building MSP. IMHO this is not only time consuming but it is also not best praxis to "hack" dll files...

Any Idea's how we could optiomize and speed up the process?

regards

peter

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

It might be worth asking the folks at E. Crane Software if their PowerGen product can help you.

Former Member
0 Kudos

Maybe you should think about not using machine code compiles. Machine code compiles are much slower, produce larger files and do not produce significant improvements in run time speed.

Try compiling the app with machine code unchecked and see how long it takes.

Former Member
0 Kudos

Hi Peter;

  You are correct - PB does not sign individual DLL's. That sounds like a great enhancement request though.

Regards ... Chris