Software Deployment Question

Com info using Wise Package Studio

12/19/2008 3668 views
I have been using Install shield for quiet some time now.
jus a few days back i started using WPS , i got issue with com extraction for the the dll ,As per the rulz we are not allowed to do anything with the custom actions for com /registration info.

could some one help me out with how to go about the com_ objects in Wise Pacakge Studio?
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

By default, WPS is set up to use the SelfReg table [shudder]. To change that, so that it extracts the COM information and populates the advertising tables instead:

- Tools/Options/Advertising/Advertising Setting
- Select 'Scan advertising information into advertising tables'
- Check the check-box 'Default to rescan advertising for new components' if you want that behaviour.

To extract on a stand-alone basis, there is an EXE in 'C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor' (the default location - yours may be different, of course) called WiseComCapture.exe. It outputs the information to a .REG output file. You can then import the .REG into your project and, when prompted, select 'Yes' to use the advertising tables.

- WCC is sometimes unable to extract COM info from some DLLs/OCXs unless WCC is called from the file's location, rather than from its installed location. A .REG of zero bytes is a pointer, so if you get such a file, try switching to the DLL/OCX's containing folder and re-run the command but calling back to WCC's container. That is, instead of::C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor> WiseComCapture /R /U [path]WHATEVER.DLL [output_path]WHATEVER.REG

you would do this:CD [path]
"C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor\WiseComCapture" /R /U WHATEVER.DLL [output_path]WHATEVER.REG
- If you end up with a .REG of less than 100 bytes, it is almost certain that the DLL has the DLLRegisterServer entry-point but no COM information. The JRE NPJAVAx.DLLs and almost *every* DLL in IBM's Client Access come to mind.
Answered 12/19/2008 by: VBScab
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ