That is kind of ironic (comical in retrospect). That's almost as secure as
"Michael Gledhill" <mikeg @ extendsys . com> wrote in message
Hi guys,
(Seven coffees later..)
Okay guys, I hope you're sitting comfortably.
I've found out what the problem is, and - trust me - it's so ridiculous,
you won't believe it.
The REASON why one of my VC++ Projects refused to run without
elevation, was because it's VC++ project name had the word "install"
in it.
That's it.
Try it.
Go into VC++ v6.0.
Create yourself a bog-standard MFC Dialog project, accept all of the
defaults, and call the project "Install". Or "Installer". Or "Mikes
wonderful Installer". Then try to compile & run it from MFC.
You won't be able to.
Vista requires elevation.
Now, try to create a second identical project, but call it just "Stall".
Or "Test". Or anything without the word "install" in it.
Compile it, run it... no elevation.
Unfortunately, having a project called, say, "Installer", but asking
VC++ to write out the .exe to, say, "Test.exe" instead of "Installer.exe"
doesn't make any difference.
Vista appears to bark at any .exe with Install or Installer within the
.exe file.
I'm stunned.. I'm absolutely stunned...
And this has wasted a huge amount of my time.
I'm quite happy that Vista is concentrating on security, but
pointlessly nagging about a project name..?!
Oh, come on...
Mike
"Michael Gledhill" wrote:
Hi MrAsm,
Thanks for the reply.
It could be possible that your project loads some DLL that requires
elevation?
I thought about this, and use the Dependency Viewer to see if there's
anything out of the ordinary. Nope, it uses exactly the same (actually
less) .dll's than one of my other projects which *does* run without
being escalated.
Yes, it's strange. But maybe there is something wrong in the code...
It seems to be more than this.
As I said, if I just hit F10, to run up until the first line of code,
the
elevation error occurs.
And if I change the very first lines of code to read:
BOOL CMikesApp::InitInstance()
{
return TRUE;
.. then exactly the same problem. An elevation is required to
run this program which does absolutely nothing !!!
This seems to suggest that it must be some kind of dependency
problem or some obscure Project Setting, but I just can't track
it down.
Have you tried to built an empty project just for test, and put the
inherited ListCtrl in it and try if it works under Vista?
Yup, and, annoying, it works a treat.
That's what so baffling... there isn't anything out of the ordinary
with this one Project, there's nothing which should shout "POTENTIAL
RISK !!" at Vista, but for some reason Vista seems to *know* there's
something dodgy about the .exe before it's even run a line of code.
Today, I'm going to resort to Plan B... strip out everything from the
project, piece by piece, under Vista stops complaining, then I'll post
an article of here, saying what the offending problem was.
And, if that doesn't work, Plan C... rebuild the project from scratch.
Then hopefully compare that .dsw file with my current one, and see
what caused the problem.
Aahh, I don't enjoy weekends like this ! Time for another coffee..
Mike