Software Deployment

(sigh...)
- Extract the OCXs from the CABs as you have already done to, say, %SYSTEMROOT%\Temp
- Use WiseComCapture to produce .REG files for the OCXs:
[path_to_Wise_EXEs]\WiseComCapture /r /u %SYSTEMROOT%\Temp\[name_of_OCX]
- Edit the .REG to properly reflect the destination path of the OCX. To explain, WiseComCapture will register the OCX as being located at %SYSTEMROOT%\Temp, whereas that might not be the actual path, so you will need to edit the path according to where the OCX will finally be installed. Remember that, in .REG files, backslahses in path names have to be 'escaped' using, er, backslash. Thus, instead of 'C:\Program Files\Foo\Bar', you would need to use 'C:\\Program Files\\Foo\\Bar'
- Import the .REG into WPS, clicking 'Yes' when asked if you want to use the Advertising tables.

However, this did not work.Could you be a little more vague? :{
Seriously, "this did not work" doesn't tell us anything: you need to be *much* more specific about what failed. Anyway, generically, to install your OCXs, they've got to come out of the CAB file at some point so I don't believe pursuing "installing the CAB files directly" is going to help you at all.

Once you had the OCXs extracted, what did you do with them? What authoring tool are you using to create the MSI?

Hello,

Well, sorry for being so vague and generic about the problem. However, i shall try to explain the problem more specifically in this attempt.

I am given few cab files that have an OCX file in each cab. So i extracted all the ocx files and included them in a package created by WISE Package Studio. I set the files to self register after they get installed.

Since these files are responsible for enabling some web based controls for MS Portfolio Server 2007, i tried to use the functionality after the install which did not work. Is there any other method through which i can do that? Maybe i use Extrac32 that is present in windows?

I hope i was able to explain the scenario in a better way than before. However, for any other clarifications, please feel free to revert back.

With Best Regards,
Tushar Singh

OK, first, the perceived wisdom is to NEVER use self-registration. Use WiseComCapture to create .REG files for the OCXs and import the .REGs into WPS. When prompted about advertising, click 'Yes'. [Waits for replies to the effect that this is total rubbish...LOL]

Next, presumably you get errors when you try to use the functionality which the OCXs provide. It would be helpfiul to know what those errors are, but I'm guessing it's to do with objects not being available. Use ProcMon (or your favourite process/registry monitor) to determine if the registry entries you expect to be present are missing when the app tries to use the object(s). If that's the case, the OCXs probably aren't being registered properly. They may have dependency on other files which are missing. Again, ProcMon will show you that or you could use Dependency Walker (not a Wise tool - find it with Google) ahead of time to check dependencies.

If you are able to install the ActiveX component by visiting the site then I would recommend doing a capturing during this event. Have done that many times with good success rate.

agree with VBScab use wisecomcapture and import the .reg files into the corresponding component. should solve your issues! ;-)

Bonjour,

Well, i have never used Wise Com Capture feature and thanks to you people to tell me that. But the problem is that i have been given the cab files only and nothing else other than the cab files. I have asked for the manual procedure to install the components so that i can figure out what needs to be done with them.

Meanwhile, i shall also figure out this Wise Com Capture thing. Maybe this assists me more in getting to the target! Will update you all with the proceedings in this.

Thanks for all your help.

With Best Regards,
Tushar Singh.

Bonjour,

Well, the job is done! i just had to register (self register). The error was due to a mis-configured server for which i was preparing the client package.

Thanks to all of you and specially to VBSCab. Although, i never asked for any inputs for Wise Com Capture as i prefer to learn by myself, but i am really greatful that he showed light to something i never knew. Will surely try this out and let you know about my experiences. Maybe we can have more information share on this.

thanks a ton!!!

With Best Regards,
Tushar Singh.

You can also import the COM by registering the ocx / dll's locally then selecting rescan advertising from the respective component (from the comment Ian made earlier about advertising)

A (ActiveX) .cab file usually also contains an .INF file used for installing the activex component.
In some rare cases it will be required to install the activex component through this .inf file as it may add additional information during installation.

Command line to install an INF file is (or right-click the file and choose install)
RunDll32.exe setupapi,InstallHinfSection DefaultInstall 132 somefile.inf

Useful links:
Creating an INF File
http://msdn2.microsoft.com/en-us/library/ms790220.aspx
(Sections of interest are "Summary of INF Sections" and "Summary of INF Directives")

RunSetupCommand Function
http://msdn2.microsoft.com/en-us/library/aa768010.aspx

ORIGINAL: matrixtushar
Well, the job is done! i just had to register (self register). (sigh...again)Take your pick from:

OK, first, the perceived wisdom is to NEVER use self-registration. Use WiseComCapture to create .REG files for the OCXs and import the .REGs into WPS. When prompted about advertising, click 'Yes'.

or:

You can also import the COM by registering the ocx / dll's locally then selecting rescan advertising from the respective component