Re: Manifests and requestedExecutionLevel
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Tue, 10 Jul 2007 09:51:34 -0400
Yes, I have seen that article, but it is completely useless. It talks about gaining
administrator rights, but that does not appear to be the same as asking for a specific
integrity level, and it handwaves about the manifest without actually telling how to
create the manifest (there is no manifest I can find in my project, just the one that
appears to be created on-the-fly and therefore could not be modified by hand, even if I
could figure out what should go in it.
I wonder why manifests are so complex that the documentation was not delivered on the day
that manifests became a component of the system. There's Something Wrong With This
Picture. I should be able to go to the MSDN, open the section on manifests, and see the
complete documentation, syntax, semantics, and examples of use. Is it there? No. I
would like to point out that it is now 2007, and VS2005 has been out for two years. Is
anyone at Microsoft taking any responsibility for this fiasco?
joe
On Mon, 9 Jul 2007 11:45:58 -0700, "David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote:
"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in messageJoseph M. Newcomer [MVP]
news:h6t49395k2e05vb7ji9bsv46sc3c6kbhs3@xxxxxxxxxx
There is a dearth of documentation on manifests, such as the little
inconsequential
details such as syntax, semantics, and methods for creating them. So I'm
stuck, and I'm
looking for advice.
The best documentation for these things is blogs. For example
http://weblogs.asp.net/kennykerr/archive/2006/09/29/Windows-Vista-for-Developers-_1320_-Part-4-_1320_-User-Account-Control.aspx
I have an app that has to run at the integrity level designated by
SECURITY_MANDATORY_MEDIUM_RID, because it wants to exchange PostMessages
with another app
running at that same level. Right now, it always starts at
SECURITY_MANDATORY_HIGH_RID.
While I can re-launch it using CreateProcessAsUser, it would be nicer if
it could launch
itself at medium integrity level, and then in the unlikely case the
co-process were
running high or low would a relaunch be necessary.
So the questions are (a) is this something the manifest will do for me?
(b) if so, what is
the correct syntax for placing it in the manifest? and (c) given that the
previous two
questions have positive answers, what is the technique of getting this
added to the
manifest that is created for me automatically by VS2005?
Kenny's article above makes it seem impossible to use a manifest to specify
a medium MIC. This will be the default for standard users but not for Admin
users (which will be High by default).
Kenny's article gives you a manifest. See the requestedExecutionLevel
section, but unfortunately there is no way to specify Medium MIC here. In
VS2005 project Properties, see the manifest tab and specify and Additional
Manifest.
-- David
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Follow-Ups:
- Re: Manifests and requestedExecutionLevel
- From: David Ching
- Re: Manifests and requestedExecutionLevel
- References:
- Manifests and requestedExecutionLevel
- From: Joseph M . Newcomer
- Re: Manifests and requestedExecutionLevel
- From: David Ching
- Manifests and requestedExecutionLevel
- Prev by Date: Re: MyDocuments folder
- Next by Date: Re: Access violation error
- Previous by thread: Re: Manifests and requestedExecutionLevel
- Next by thread: Re: Manifests and requestedExecutionLevel
- Index(es):
Relevant Pages
|