Re: ActiveX create problem in Vista
- From: "Kevin Provance" <casey@xxxxxxxxxxx>
- Date: Wed, 1 Aug 2007 10:30:02 -0400
Heh...well, it certainly would be a repeat business when those same clients
call back with spyware and malware problems.
Don't get me wrong, I don't care for all that extra BS on Vista either...but
I have seen a lot less problems of this sort with the few customers I have
who are using Vista. As soon as MS finds the perfect balance...if only.
<g>
"mayayana" <mayaXXyana1a@xxxxxxxxxxxxxxxx> wrote in message
news:OgI02EE1HHA.748@xxxxxxxxxxxxxxxxxxxxxxx
|
| > I'm only telling you what I doi, and it works for me. If you find
another
| > way, please share it
|
| I got thinking about that. It seems a shame to have
| to create a setup just to distribute components. And
| David Youngblood's option sounds like a lot of trouble -
| at least more trouble than a drag-drop.
|
| Three options that might be worth exploring, but will
| still require writing some code to make them easy:
|
| 1) The Registry entries can be done "by hand". The
| downside of that, though, is that you need to know the
| entries beforehand. It would work fine in an installer,
| but not as a quick and easy substitute for a RegSvr32
| command line.
|
| 2) The PDW uses vb6stkit.dll to do a number of custom
| operations. One of those is a function DLLSelfRegister,
| which is called in the RegisterFiles sub of Setup1.
| It's a very simple call that just takes the file path.
| Looks easy enough, but still requires writing a small
| tool if it's going to be used with drag-drop ease. And
| vb6stkit.dll will only exist on machines that have had
| some kind of VB6 installation.
|
| 3) Matthew Curland provides direct API sample code
| in his EditTLB source code from the Advanced VB book.
| It uses LoadTypeLibEx to get an iTypelib pointer, which
| is then used to call RegisterTypeLib. I haven't looked at
| it thoroughly, so I don't know whether those are just
| straight calls or whether they use his assembly code
| tricks, etc.
|
| So I can't just tell people to "drop the component on
| this RegSvr script before using". But it looks like I could
| write a very small EXE and tell them to drop the component
| onto that in order to register it.
|
| The more I hear about Vista, the more it seems like the
| real solution is to just simply turn all that "security" off.
| I can't imagine that the general public is going to put up
| with all these problems. I suspect there'll soon be money
| to be made with a quickie tech. service:
| "Fix Your Vista - Only $29.99!!"
| And the service will consist of configuring Vista to work
| like XP, running as real admin. with no UAC, etc.
|
|
.
- References:
- Re: ActiveX create problem in Vista
- From: Kevin Provance
- Re: ActiveX create problem in Vista
- From: mayayana
- Re: ActiveX create problem in Vista
- From: Kevin Provance
- Re: ActiveX create problem in Vista
- From: mayayana
- Re: ActiveX create problem in Vista
- Prev by Date: Re: Help for a VB prog
- Next by Date: Re: Help for a VB prog
- Previous by thread: Re: ActiveX create problem in Vista
- Next by thread: Re: ActiveX create problem in Vista
- Index(es):
Relevant Pages
|
