Software Deployment

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.

Notes:
- 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.