Re: Compiling DLL & Vista: Follow up
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Sat, 3 Mar 2007 04:35:54 -0600
"Kevin Provance" <casey@xxxxxxxxxxx> wrote in message
news:Om2H23UXHHA.1388@xxxxxxxxxxxxxxxxxxxxxxx
Well Mike...if you remember, I'm the type of guy who will just forcus on ason,
problem until I've got it fixed and everything else be damned (minus my
of course). I've been studying Vista all day. MSDN, newgroups, Google,you
name it and I think I'm starting to get a grasp on the monster I am upwon't
against, and it ain't pretty.
Apparently, running as an Admin or setting a program to run as Admin will
encourage the UAC prompt, where as running as a standard user won't (ass
backwards, ain't it?) The more privlidges you give yourself, the more
prompts you get.
The biggest problem I've found in my cool little registry hack to register
and unregister ActX DLLs and OCXs by double-clicking on the given file
work with Vista because one cannot set regsvr32 to run ad admin. The filemy
prevents it (hard coded that way I am guessing). So, to properly register
all the ActX stuff requires loading it up and compiling...which becomes
tedious after awhile. Because I keep all my code on the XP box and load
code via the network I had to set sharing privlidges on XP to accomodatethe
Vista box. I'd hate to have to have two separate code bases, one on eacha
box to work off of, so for now that's how I'm doing it.
Try reading the Vista newsgroups....lots of complaining about the UAC.
Ultimately I will shut it off, but for now I am running with the least
privlidges as to ensure a properly running program as most users will
ultimately be running the same. Provided things go well under those
settings, being an Admin should be a breeze.
So yeah, Vista is really picking about ActiveX, registry writing and file
writing. The Developer Best Practices and Guidelines for Applications in
Least Privileged Environment artivle is a real help and worth reading.:-)
- Kev
<snipped>
Just another OT comment to let you know you are not alone.
I'm also having to fight it out with UAC - which is somewhat embarressing as
I, after piddling with pre-released versions of Vista, avowed quite loudly
in this group and at work that I would absolutely nothing to do with Vista
until at least SP2. <insert sound of someone eating crow>
The new 'security' features of Vista are of interest to my client because
they have dozens, if not hundreds, of projects/programs developed over the
years - each with their own slight variations on where to put things etc.
There have been multiple attempts to apply single enterprise-wide solutions,
but like all such schemes are dependent on voluntary adoption of
conventions. The idea that the OS would enforce a De Facto standard has
appeal.
Or so the theory goes. <g>
Problem is there doesn't seem to be any "De Facto" standard. Or rather I am
having trouble seeing one. (I see the swatches and recognize the various
stitches, but can't quite see the quilt.) The 'fixes' are as ad hoc and
diverse as the original conventions we are seeking to resolve. Also as I put
a pencil to it, adopting to UAC ain't going to be cheap. If we turn it off,
what was the point of going there in the first place?
Meanwhile, the UNIX crowd are ROFLTAO!
-ralph
.
- Follow-Ups:
- Re: Compiling DLL & Vista: Follow up
- From: Kevin Provance
- Re: Compiling DLL & Vista: Follow up
- From: mayayana
- Re: Compiling DLL & Vista: Follow up
- References:
- Compiling DLL & Vista
- From: Kevin Provance
- Re: Compiling DLL & Vista: Follow up
- From: Kevin Provance
- Re: Compiling DLL & Vista: Follow up
- From: MikeD
- Re: Compiling DLL & Vista: Follow up
- From: Kevin Provance
- Compiling DLL & Vista
- Prev by Date: Re: using Line Input
- Next by Date: Re: InStr anomaly?
- Previous by thread: Re: Compiling DLL & Vista: Follow up
- Next by thread: Re: Compiling DLL & Vista: Follow up
- Index(es):
Relevant Pages
|