Re: ActiveX create problem in Vista
- From: "Kevin Provance" <casey@xxxxxxxxxxx>
- Date: Tue, 31 Jul 2007 22:29:16 -0400
You guys keep mentioning this ActiveX Installer service, but I have no such
service on my Vista box and I do not have any problems with my ActiveX
stuff, DLLs or OCXs. Somehow, I don't think it plays into it as much as you
think.
Here is what I know (which I will be documenting on a web site very soon)
through much trial and error.
VB6.EXE must be run as adminstrator, no if and or buts about it. This can
be accomplished by going into that file's properties, then compatibility
settings and ticking the "start as adminstrator" setting. Or you could
write a Vista manifest for it, but I'd stick with the first for now. If
this is not done, VB6 won't write all the necessary COM who-ha to the
registry as needed to use ActX stuff (and will get registry error and such
as a result).
Now this is the important part: In the past, most folks could just drop
their ActiveX stuff on another box and register is manually, using any
different method available. To date, none of these will work unless you
really mess around with various system settings. In other words, all the
neat tricks we used to use on XP and lower will not work on Vista. Which
leaves one of two ways to properly register ActiveX DLL and OCXs on Vista.
1) Open the actual project in a properly set VB6 environment and compile it.
That typically will do the job. If that is not possible then...
2) You *must* install the Active X components on the Vista machine using a
proper setup deployment program. So far, I've not messed with the
deployment wizard available with VB and VS...it's a piece of crap anyway.
What I do to get all my OCXs and DLLs properly installed in Vista is I wrote
a setup script using Inno Setup (free and Vista compatible) and physically
install the files myself. Because Inno works great with Vista, and because
I spent some time tweaking my install script to get those damned files
installed with no headaches, I think I have it down without major issues.
I've had a couple people test my script on their Vista system and the files
seems to install and run just fine. Inno has a few tricks in it's setup to
play nice with Vista in terms of how and where files are installed,
including starting itself up in admin mode so those files do get installed
properly and not forcing the end user to do it themselves.
Now, another thing worth noting is the location of the where you install
your activeX files physically on the drive. Vista is very fickle about
this, and after reading all the infor MS has posted about it (combined with
my own tests), the short of it is this: When you install your own hand
rolled ActiveX stuff, it works better if you install them either in your
apps own folder or your own folder in the Common folder found within the
Program Files folder. See, the was never a big deal or strictly enforced
before Vista and everyone seemed content just to install all DLL and OCX
files in the System folder, whatever that was on any given system. I tried
doing that once and had nothing but trouble. When I started properly
installing my ActiveX stuff in the Common folder or my apps folder, those
problems went away. So when it comes to files that require registration of
that kind, I no longer use the System folder (even if MS once said that's
what would should do...same people who promote INI files...again)
Eh...did any of that make sense? It's been working for me so far, and
believe me when I say I have put more than a few months of research and
trial and error into getting VB6, my apps and Vista to all play well
together...so hopefully this well help you out too.
If you decide to go the Inno setup route, I'll be happy to post a copy of
what I use to get my stuff installed and running.
- Kev
"Steve Easton" <admin@xxxxxxxxxxxxx> wrote in message
news:ORjWaT70HHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
|
| "Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:OsPHY$50HHA.4928@xxxxxxxxxxxxxxxxxxxxxxx
| >
| > "Steve Easton" <admin@xxxxxxxxxxxxx> wrote in message
| > news:uoLKk250HHA.3848@xxxxxxxxxxxxxxxxxxxxxxx
| >>
| >> "Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
| > news:uUWV%23s40HHA.5736@xxxxxxxxxxxxxxxxxxxxxxx
| >> >
| >> > "Steve Easton" <admin@xxxxxxxxxxxxx> wrote in message
| >> > news:eWGAFi40HHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
| >> >> Is the ActiveX installer service installed and enabled on the Vista
| >> > machine?
| >> >>
| >> >> --
| >> >>
| >> >> Steve Easton
| >> >>
| >> >
| >> > AxIS allows users without administrative priviledges to install
ActiveX
| >> > components and therefore wouldn't address the OP's specific problem.
| >> > However, if it did resolve the problem... then we would be looking at
| >> > perhaps an even bigger issue. <g>
| >> >
| >>
| >> Yes it does Ralph, but it has to be manually installed and then the
| > service has to be enabled.
| >> It is not installed by default when the OS is installed.
| >>
| >
| > I am just being picky. <smile>
| >
| > The point is the OP's problem isn't the User being able to install
ActiveX
| > components without Administrative priviledges. It is that when installed
| > WITH adminstrative priviledges the app doesn't work. Even if the app
started
| > working with AxIS running, the OP, as a developer and distributer of
| > software, will still have to go back and find out why he can't install
the
| > components in the first place, else live with an unresolved issue and
| > essentially a quick but unkown fix.
| >
| > Having fought a few of these battles already, trust me, it plays hell
with
| > creating and distributing base images, and tends to raise a few
eyebrows.
| > <g>
| >
| > -ralph
|
| OK, my understanding is that you simply can't install active x unless the
AxIS is running.
| You might be able to write the files to the machine with an installer
without AxIS installed, but unless
| AxIS is installed and enabled activeX will fail to initialize.
|
| Do I have it wrong?
|
| --
|
| Steve Easton
|
|
|
.
- Follow-Ups:
- Re: ActiveX create problem in Vista
- From: Steve Easton
- Re: ActiveX create problem in Vista
- From: mayayana
- Re: ActiveX create problem in Vista
- Prev by Date: Re: how do people feel about exit function from loop
- Next by Date: Re: Regarding Hooking MouseWheel event....
- Previous by thread: Re: ActiveX create problem in Vista
- Next by thread: Re: ActiveX create problem in Vista
- Index(es):
Relevant Pages
|
Loading
