Using Manifest File in PowerBuilder 5

[Former Member]

Hi,

We are working in an old project which was developed in PowerBuilder 5.0,

We followed the below steps to get the list of DLL and OCX getting register with our Application

1. Searched in application installation path.

2. Searched in source code.

Is there any other way to get the list of components and reference list?

We need the above list to create manifest file.

We have another big challenge that whether Manifest file is work with PB5 or not? If yes,how to make PB5 app to communicate with manifest?

Please help...

Thanks,

Sundar

[Former Member]

Hi,

Please let me know,

Is there any other way to get the list of components and reference ( DLL & OCX ) used in PB5 application?

Thanks,

Sundar

[Former Member]

Please tell us the version of Windows you are using and why you think you need a manifest file. There may be another way to get past your problem that doesn't involve manifest files.

[Former Member]

Roland,

I am using Windows 7. I am working in a Windows 7 migration project(from Windows XP to Windows 7).

Other applications in my project using manifest file for their DLLs and OCX.

So I forced to use manifest in my PB5 application.

I tried to create a side by side application manifest file, but got an error "Pbroi050.DLL is not self register"

Thanks,

Sundar

[Former Member]

Hi Sundar;

  FWIW: PB 5 is not W7 compatible and PowerBuilder was not until at least version 11.5.1.

Bottom line ... You need to upgrade.  

Regards ... Chris

[CobyKako]

Hello Sundar,

PBROI050.DLL was used for OLE 2.0 support: Creating PowerBuilder executable

I don't remember if it was not possible to self-register this DLL with regsvr32. I guess you had to use additional files to accomplish the task: New in PowerBuilder 5 - Inbound OLE Automation

But I completely agree with Chris : do not risk to use PB5 on Win7...

Kind regards,

Jacob

[Former Member]

Only files that implement an OLE control need to be registered. That PowerBuilder file gives your app the ability to connect to OLE controls but does not implement a control itself. Therefore it does not need to be registered. None of the PowerBuilder runtime files need to be registered.

[Former Member]

Roland,

Please help me to find third party DLL and mention the DLLs to be register.

I hope that the below dlls are related to PowerBuilder 5.0 and need not to register

Pbbgr050.dll, Pbdbt050.dll, Pbdwe050.dll, Pbodb050.dll, Pbroi050.dll, Pbrtc050.dll, Pbrte050.dll, Pbrtf050.dll, Pbshr050.dll, Pbtyp050.dll

I have doubt on following DLLs and ocx

msvcrt.dll, MSVCRT40.dll, OLEPRO32.dll, Pfccom32.dll, CTDATE32.ocx

Please confirm above 4 DLLs and 1 OCX are need to register?

Thanks,

Sundar

[Former Member]

The PBxxx050.DLL files do not need to be registered and will show an error message if you try. Registration isn't something that all .dll files can do automatically. The author of the dll has to code certain functions into the dll that implement the registration process. All the regsvr32 program does is call those functions within the dll.

The ocx file is the only one that would need to be registered.

[former_member190719]

You need to create an external manifest file, and ensure that PowerBuilder does not try to generate an internal one in the executable.  Forturnately, I don't believe PB 5 could do that.  It only started becoming an option when PB introduced support for new style controls.

As long as the manifest file has the same name as the PowerBuilder generated executable with a ".manifest" extension, Windows will use it.  It's not a question of whether or not PowerBuilder will work with it, but whether Windows will. Of course, you have to be a on fairly recent version of Windows.  If you're still using PowerBuilder 5, you might still be using Windows 95.  What version of Windows are you using?

Manifest files are pretty tricky to put together by hand.  I suggest looking at something like Side by Side Manifest Maker that will generate them for you.

[Former Member]

Hi Sundar;

1) PB did not support .Net SDK manifest files until v11.1.

2) You can try something like like this ...

Answers to Several Application Manifest Mysteries and Questions - Pat's Windows Development...

=> I have no idea if this works with old PB EXE's though.

Good luck!

Regards ... Chris