a customer of ours has asked me to provide a silent install package for BO XI r2 + service packs.
thanks to the info found over here, no problem to do this on a clean machine.

thing is the customer wants this version to coexist on systems that will still have a manual installed version of BO ent v 6 (other folders).

when I test my package on a system with bo 6 installed, it fails to register the files importent6;dll and exportsdk.dll.

I could throw them out of the selfreg table, but how sure can I be that everything will still work fine ?
I mean sooner or later the package for BO XI will be installed on clean machines also where those files then will not be registered ...

any advice or practical experience ?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Always throw EVERYTHING out of the SelfReg table! The problem with using it (or RegSvr32 in a Custom Action) is that anything which has a dependency which isn't present will fail to register.

Use your authoring tool's utilities to extract the COM information from the DLLs and OCXs listed in the SelfReg table into .REG files, import the .REGs into your project and, if prompted, elect to use the advertising tables instead of the Registry table. Then delete the SelfReg table.
Answered 10/08/2008 by: VBScab
Red Belt

Please log in to comment
As Ian says you can use wisecomcapture.exe to get the reg information instead of using selfreg. Also I've noticed that Wise mistakenly puts dlls which can't be registered into the selfreg table. That's probably when you see an error. If you get one of these the wisecomcapture output file will be blank.

If you've got BO XI then it must be really smelly there where you work. I've found that a good deodorant will bring my BO down to II or III......
Answered 10/08/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Also I've noticed that Wise mistakenly puts dlls which can't be registered into the selfreg table. Well.....maybe not 'mistakenly' - 'lazily' is better.

WiseComCapture checks for the DLLRegisterServer entry-point and, if found, assumes that a file contains COM information. That's lazy programming, as there are additional checks that can be made to ensure that that's the case, removing the need for any assumption. Still, we're stuck with it: I can't see Wise changing that within our lifetimes, given that there are still open tickets on v5.6 bugs/issues.
Answered 10/09/2008 by: VBScab
Red Belt

Please log in to comment