I created a .Net DLL (COM) and managed to use it in PowerBuilder (12.5 Classic)... so far so good...
The downside that we need te register this DLL in order to be able to use it.
I've read that there's possibility to use such a DLL without registration: this via the creation/use of manifests.
Can anyone help me on this and explain what I need to do (and how) in order to be able to use the Net DLL (COM) in PowerBuilder without registration?
Any examples maybe?
The things I've (already) read are not really clear/straightforward: I can't make it work at the moment...
Anyone with experience with this (and willing to help)?
Thanks in advance,
Marc.
I believe the enbedded manifest files mimic the registry setting so the GUID is probably still used, though it probably doesn't have to be unique. However the dll can still be registered with regasm should anyone want to do so, so I would still use it as it it was a non-side-by-side COM dll to aloow the choice of how to use it.
I have never signed an assembly, so I guess it's not important to get this to work :)
Yes, I have always had to put the assembly in the same folder as the executable, I guess it may be possible in the manifest file to point to a folder, but I haven't seen anyone ever do that.
As far as I know the manifest file will alway be separate from the PowerBuidler application, but I've found that quite useful as the version number in there allows you to control which version of the assembly it is expecting to find, and for a quick bug fix sometimes its nice to be able to update the manifest file with a new version number