/build/static/layout/Breadcrumb_cap_w.png

ActiveX Addons

Hi All, I am new to the svs arena so I am still working out what can and can't be done. Please forgive me if this is a stupid question :-)
I have an application the installs a ActiveX addon for Internet Explorer which shows up in IE's addon manager as an approved addon. When I captured this program as a Virtual Package using Wise the ActiveX addon does not show up when I activate the layer. I used InstallWatch to capture the differences between the Virtual Package and a manual install and came out with a bunch of HKLM reg entries. If I activate the Virtual Package and then manually import the registry entries to the PC the addons show up but if I import those same reg entries into the Virtual Package the addons still don't appear.
Are ActiveX addons something that can't be handled in a Virtual Package or is there an extra step I am missing to get this working. At the moment I am assuming it can't be done so I will be reverting back to a standard msi package but i would love to know for a fact that this is the case.
Thanks in advance for any assistance you can offer.
Justin
[/align]

0 Comments   [ + ] Show comments

Answers (7)

Posted by: BadShadd 16 years ago
Orange Senior Belt
0
I'm not a SVS user, but you can capture / virtualize ActiveX controls with SoftGrid so I would think that SVS should be able to handle it.
Posted by: AngelD 16 years ago
Red Belt
0
I havn't done AX (ActiveX) and IE that much but my guessing is that you run IE from base and therefore does not see the layered AX component.
Try running IE from within the AX layer using SVSCMD and see if that helps.
Posted by: PuterFix.biz 16 years ago
Senior Yellow Belt
0
Thanks for the replies.

After some more testing tonight I finally managed to locate the fix. There is a registry key similar to the one below written for each ActiveX addon:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved\{1A69C109-5E65-4ad7-80BB-026EBB8C0972}]

I don't know why but for some reason Wise did not pick these entries up. Also when I used Installwatch to capture the registry changes between the Manual and Virtual installs these keys were in there but they don't import into the package. After pulling the capture reg file apart I worked out these keys made the difference so i then went through and manually added them to my package.....low and behold it all now works. :-)
Posted by: kapil.kathuria 16 years ago
Orange Belt
0
ORIGINAL: BadShadd

I'm not a SVS user, but you can capture / virtualize ActiveX controls with SoftGrid so I would think that SVS should be able to handle it.


How can we do it using SoftGrid?

Lets say I have created a package for IE7 and now i need to add a addon to it. For this addon I create a separate package. How can I make sure that launching IE from IE7 package will also load this Addon as well?
Posted by: BadShadd 16 years ago
Orange Senior Belt
0
IE7 is part of our base load for all systems so I only captured the AX installation & made a separate IE icon for it.
Posted by: kapil.kathuria 16 years ago
Orange Belt
0
hmmm... If we have multiple Addons:
1. I believe making separate icon, for IE for each addon, would not make sense.
2. In case requirement is to use multiple addon together, how do we handle this?

I was wondering there should be better way to handle this.
Posted by: critic 16 years ago
Yellow Belt
0
[font="times new roman"]
hi,

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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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