Install ocx best practice
We have a website that requires what I believe to be an active x control to be installed. Our users are not permitted to install active x components through the web. From all the reading I've done on Active x I'm still not sure if this is an active x component since most of the documentation I've read talks about a cab and inf files to install. The only file is an .ocx file. I can register this file manually using regsvr32.exe and the webpage will work. If I install the ocx from the website a file gets created in the Downloaded Program Files directory. I don't know if this is necessary to have or not?. How is this usually handled? Do I just treat it as a standard ocx file in my package?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
WayneB
15 years ago
Hey Joe,
In short - Yes.
Are you using Wise? Then you don't need to run resvr32 in your package. I usually place these files in the 'CommonFilesFolder\ApplicationName" and register the .ocx from the file path. When installed through your deloyment tool, you'll see it in your managed add-ons in your browser (IE, not sure about FF?).
Have fun,
Wayne
In short - Yes.
Are you using Wise? Then you don't need to run resvr32 in your package. I usually place these files in the 'CommonFilesFolder\ApplicationName" and register the .ocx from the file path. When installed through your deloyment tool, you'll see it in your managed add-ons in your browser (IE, not sure about FF?).
Have fun,
Wayne
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
