I have an app that needs to run with elevated privileges on
Windows Vista (Registry operations - don't ask).
I have added a manifest file that looks like this:
---snip---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86"
name="myapp" type="win32"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
---snip---
(where 'myapp' has been replaced with the proper name, of course)
and I have configured this post-build event:
---snip---
"$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest
"$(ProjectDir)$(TargetName).exe.manifest"
–outputresource:"$(TargetDir)$(TargetFileName)";#1
---snip---
I am using mt.exe version 5.2.3790.2075.
On Windows Vista (running as a WMware virtual machine),
it pops up the User Account Control dialog EVERY time I run the app
- not just the first time.
As far as I remember, this was not the case a short while ago (weeks
or months?) I am sure that when I originally added the manifest,
Vista would only bring up the dialog once for each new build.
I have not changed the manifest file, the build process, the program
version, or anything else I can think of at the development end that
could cause this change/difference.
Has anything changed on the Vista side, e.g. as the result of a
Windows Update, or where should I look for clues to the change
in this behavior?
Or does my memory fail me and it never worked in the first place?
TIA,
Joergen Bech 9 1774
Joergen,
In my idea you have the same idea as I had some days ago, but I don't think
that this newsgroup is the right place for this question. More your local
Microsoft office.
-:)
Cor
"Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAMschreef in bericht
news:pm********************************@4ax.com...
>
I have an app that needs to run with elevated privileges on
Windows Vista (Registry operations - don't ask).
I have added a manifest file that looks like this:
---snip---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86"
name="myapp" type="win32"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
---snip---
(where 'myapp' has been replaced with the proper name, of course)
and I have configured this post-build event:
---snip---
"$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest
"$(ProjectDir)$(TargetName).exe.manifest"
-outputresource:"$(TargetDir)$(TargetFileName)";#1
---snip---
I am using mt.exe version 5.2.3790.2075.
On Windows Vista (running as a WMware virtual machine),
it pops up the User Account Control dialog EVERY time I run the app
- not just the first time.
As far as I remember, this was not the case a short while ago (weeks
or months?) I am sure that when I originally added the manifest,
Vista would only bring up the dialog once for each new build.
I have not changed the manifest file, the build process, the program
version, or anything else I can think of at the development end that
could cause this change/difference.
Has anything changed on the Vista side, e.g. as the result of a
Windows Update, or where should I look for clues to the change
in this behavior?
Or does my memory fail me and it never worked in the first place?
TIA,
Joergen Bech
On May 19, 1:39*pm, Joergen Bech <jbech<NOSPAM>@<NOSPAM>post1.tele.dk>
wrote:
I have an app that needs to run with elevated privileges on
Windows Vista (Registry operations - don't ask).
I have added a manifest file that looks like this:
---snip---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
* *<assemblyIdentity version="1.0.0.0" processorArchitecture="X86"
name="myapp" type="win32"/>
* * * <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
* * * <security>
* * * * *<requestedPrivileges>
* * * * * * <requestedExecutionLevel level="requireAdministrator"/>
* * * * *</requestedPrivileges>
* * * </security>
* *</trustInfo>
</assembly>
---snip---
(where 'myapp' has been replaced with the proper name, of course)
and I have configured this post-build event:
---snip---
"$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest
"$(ProjectDir)$(TargetName).exe.manifest"
–outputresource:"$(TargetDir)$(TargetFileName)";#1
---snip---
I am using mt.exe version 5.2.3790.2075.
On Windows Vista (running as a WMware virtual machine),
it pops up the User Account Control dialog EVERY time I run the app
- not just the first time.
As far as I remember, this was not the case a short while ago (weeks
or months?) I am sure that when I originally added the manifest,
Vista would only bring up the dialog once for each new build.
I have not changed the manifest file, the build process, the program
version, or anything else I can think of at the development end that
could cause this change/difference.
Has anything changed on the Vista side, e.g. as the result of a
Windows Update, or where should I look for clues to the change
in this behavior?
Or does my memory fail me and it never worked in the first place?
TIA,
Joergen Bech
Vista's UAC annoys even an end user on usage of every software. I
recommend you to disable it.
Here is how to: http://www.petri.co.il/disable_uac_in_windows_vista.htm
Thanks,
Onur Güzel
"kimiraikkonen" <ki*************@gmail.comwrote in message
news:70**********************************@m45g2000 hsb.googlegroups.com...
On May 19, 1:39 pm, Joergen Bech <jbech<NOSPAM>@<NOSPAM>post1.tele.dk>
wrote:
I have an app that needs to run with elevated privileges on
Windows Vista (Registry operations - don't ask).
I have added a manifest file that looks like this:
---snip---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86"
name="myapp" type="win32"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
---snip---
(where 'myapp' has been replaced with the proper name, of course)
and I have configured this post-build event:
---snip---
"$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest
"$(ProjectDir)$(TargetName).exe.manifest"
–outputresource:"$(TargetDir)$(TargetFileName)";#1
---snip---
I am using mt.exe version 5.2.3790.2075.
On Windows Vista (running as a WMware virtual machine),
it pops up the User Account Control dialog EVERY time I run the app
- not just the first time.
As far as I remember, this was not the case a short while ago (weeks
or months?) I am sure that when I originally added the manifest,
Vista would only bring up the dialog once for each new build.
I have not changed the manifest file, the build process, the program
version, or anything else I can think of at the development end that
could cause this change/difference.
Has anything changed on the Vista side, e.g. as the result of a
Windows Update, or where should I look for clues to the change
in this behavior?
Or does my memory fail me and it never worked in the first place?
TIA,
Joergen Bech
Vista's UAC annoys even an end user on usage of every software. I
recommend you to disable it.
Here is how to: http://www.petri.co.il/disable_uac_in_windows_vista.htm
Thanks,
Onur Güzel
Really have to disagree with what you are showing here. While I have
disabled it the most irritating thing about any software is that it will
reconfigure your system to something you do not want. If the user has a
problem then they will setup their workstation to their particular settings.
Changing that is just rude. If they complain you can point out how to
change it but doing it otherwise is not wise.
Just my thought
LS
Thank you for taking the time to reply, but I do not see how your
reply is of any help at all.
1) What idea did you have a few days ago? Was it posted here?
2) We are talking about a VB.Net 2005 application and manifest files.
What would be a better group than the general VB.Net one?
3) What do you mean by "my local Microsoft office"?
I presume English is not your first language. Did something get lost
in translation?
Sorry,
Joergen Bech
On Tue, 20 May 2008 06:44:10 +0200, "Cor Ligthert[MVP]"
<no************@planet.nlwrote:
>Joergen,
In my idea you have the same idea as I had some days ago, but I don't think that this newsgroup is the right place for this question. More your local Microsoft office.
-:)
Cor
"Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAMschreef in bericht news:pm********************************@4ax.com.. .
>> I have an app that needs to run with elevated privileges on Windows Vista (Registry operations - don't ask).
I have added a manifest file that looks like this: ---snip--- <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="myapp" type="win32"/> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="requireAdministrator"/> </requestedPrivileges> </security> </trustInfo> </assembly> ---snip---
(where 'myapp' has been replaced with the proper name, of course)
and I have configured this post-build event: ---snip--- "$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest "$(ProjectDir)$(TargetName).exe.manifest" -outputresource:"$(TargetDir)$(TargetFileName)";#1 ---snip---
I am using mt.exe version 5.2.3790.2075.
On Windows Vista (running as a WMware virtual machine), it pops up the User Account Control dialog EVERY time I run the app - not just the first time.
As far as I remember, this was not the case a short while ago (weeks or months?) I am sure that when I originally added the manifest, Vista would only bring up the dialog once for each new build.
I have not changed the manifest file, the build process, the program version, or anything else I can think of at the development end that could cause this change/difference.
Has anything changed on the Vista side, e.g. as the result of a Windows Update, or where should I look for clues to the change in this behavior?
Or does my memory fail me and it never worked in the first place?
TIA,
Joergen Bech
On Tue, 20 May 2008 15:15:07 -0400, "Lloyd Sheen" <a@b.cwrote:
---snip---
> Vista's UAC annoys even an end user on usage of every software. I recommend you to disable it. Here is how to: http://www.petri.co.il/disable_uac_in_windows_vista.htm
Thanks,
Onur Güzel
Really have to disagree with what you are showing here. While I have disabled it the most irritating thing about any software is that it will reconfigure your system to something you do not want. If the user has a problem then they will setup their workstation to their particular settings. Changing that is just rude. If they complain you can point out how to change it but doing it otherwise is not wise.
Just my thought LS
I agree. I have no say in how my end users should configure their
systems and I certainly do not want to suggest or recommend that
they change their system settings to something that makes it less
secure.
As the app is only going to be used in enterprise scenarios, the
machines are likely to be managed by a local system administrator,
so in all probability, this is not even an option.
Regards,
Joergen Bech
Thanks to those who replied, but I solved it another, more proper,
way:
I changed the requestedExecutionLevel to "asInvoker" and rewrote
the portions of the program that required the elevated permissions
(writing global settings to the Application Data folder instead of
writing to the Registry's HKLM node, and writing other files to the
same folder instead of the application's program folder).
I had reasons for doing things the old way, but in the end, following
best practices proved to be the path of least resistance.
Regards,
Joergen Bech
On Mon, 19 May 2008 12:39:39 +0200, Joergen Bech
<jbech<NOSPAM>@<NOSPAM>post1.tele.dkwrote:
> I have an app that needs to run with elevated privileges on Windows Vista (Registry operations - don't ask).
I have added a manifest file that looks like this: ---snip--- <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="myapp" type="win32"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator"/>
</requestedPrivileges>
</security>
</trustInfo> </assembly> ---snip---
(where 'myapp' has been replaced with the proper name, of course)
and I have configured this post-build event: ---snip--- "$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest "$(ProjectDir)$(TargetName).exe.manifest" –outputresource:"$(TargetDir)$(TargetFileName)";# 1 ---snip---
I am using mt.exe version 5.2.3790.2075.
On Windows Vista (running as a WMware virtual machine), it pops up the User Account Control dialog EVERY time I run the app - not just the first time.
As far as I remember, this was not the case a short while ago (weeks or months?) I am sure that when I originally added the manifest, Vista would only bring up the dialog once for each new build.
I have not changed the manifest file, the build process, the program version, or anything else I can think of at the development end that could cause this change/difference.
Has anything changed on the Vista side, e.g. as the result of a Windows Update, or where should I look for clues to the change in this behavior?
Or does my memory fail me and it never worked in the first place?
TIA,
Joergen Bech
Joergen,
Office is in Danish "Kontor", not a Microsoft product,
Denmark
The Denmark office supports: Faroe Islands, Greenland, Iceland
For the rest, it has no sense to reply to you, as you know everything better
than anybody else.
Cor
"Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAMschreef in bericht
news:e7********************************@4ax.com...
>
Thank you for taking the time to reply, but I do not see how your
reply is of any help at all.
1) What idea did you have a few days ago? Was it posted here?
2) We are talking about a VB.Net 2005 application and manifest files.
What would be a better group than the general VB.Net one?
3) What do you mean by "my local Microsoft office"?
I presume English is not your first language. Did something get lost
in translation?
Sorry,
Joergen Bech
On Tue, 20 May 2008 06:44:10 +0200, "Cor Ligthert[MVP]"
<no************@planet.nlwrote:
>>Joergen,
In my idea you have the same idea as I had some days ago, but I don't think that this newsgroup is the right place for this question. More your local Microsoft office.
-:)
Cor
"Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAMschreef in bericht news:pm********************************@4ax.com. ..
>>> I have an app that needs to run with elevated privileges on Windows Vista (Registry operations - don't ask).
I have added a manifest file that looks like this: ---snip--- <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="myapp" type="win32"/> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="requireAdministrator"/> </requestedPrivileges> </security> </trustInfo> </assembly> ---snip---
(where 'myapp' has been replaced with the proper name, of course)
and I have configured this post-build event: ---snip--- "$(DevEnvDir)..\..\SDK\v2.0\bin\mt.exe" -manifest "$(ProjectDir)$(TargetName).exe.manifest" -outputresource:"$(TargetDir)$(TargetFileName)";#1 ---snip---
I am using mt.exe version 5.2.3790.2075.
On Windows Vista (running as a WMware virtual machine), it pops up the User Account Control dialog EVERY time I run the app - not just the first time.
As far as I remember, this was not the case a short while ago (weeks or months?) I am sure that when I originally added the manifest, Vista would only bring up the dialog once for each new build.
I have not changed the manifest file, the build process, the program version, or anything else I can think of at the development end that could cause this change/difference.
Has anything changed on the Vista side, e.g. as the result of a Windows Update, or where should I look for clues to the change in this behavior?
Or does my memory fail me and it never worked in the first place?
TIA,
Joergen Bech
Yes, I know the difference between "office" and "Office", but
could not tell what, if anything, it had to do with my problem.
No, I do not know everything. I post here because helpful
people like yourself often have provided nuggets of gold to
get me past an obstacle.
I was genuinely puzzled by your reply and thought it might
refer to an inside joke I was not privy to. English is not *my*
first language either and, from time to time, I have found that
a few more exchanges are necessary for clarification, esp.
when a message has to be translated twice when passed
from sender to receiver. No disrespect intended.
At any rate, the problem was solved at the root, but I would
still be happy to see someone jump in and complete the thread
by answering the original question so others googling for a
solution to the same problem do not find this thread to be
another dead end.
Regards,
Joergen Bech
On Wed, 21 May 2008 06:04:00 +0200, "Cor Ligthert[MVP]"
<no************@planet.nlwrote:
>Joergen,
Office is in Danish "Kontor", not a Microsoft product,
Denmark
The Denmark office supports: Faroe Islands, Greenland, Iceland For the rest, it has no sense to reply to you, as you know everything better than anybody else.
Cor
---snip---
OK
"Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAMschreef in bericht
news:k2********************************@4ax.com...
>
Yes, I know the difference between "office" and "Office", but
could not tell what, if anything, it had to do with my problem.
No, I do not know everything. I post here because helpful
people like yourself often have provided nuggets of gold to
get me past an obstacle.
I was genuinely puzzled by your reply and thought it might
refer to an inside joke I was not privy to. English is not *my*
first language either and, from time to time, I have found that
a few more exchanges are necessary for clarification, esp.
when a message has to be translated twice when passed
from sender to receiver. No disrespect intended.
At any rate, the problem was solved at the root, but I would
still be happy to see someone jump in and complete the thread
by answering the original question so others googling for a
solution to the same problem do not find this thread to be
another dead end.
Regards,
Joergen Bech
On Wed, 21 May 2008 06:04:00 +0200, "Cor Ligthert[MVP]"
<no************@planet.nlwrote:
>>Joergen,
Office is in Danish "Kontor", not a Microsoft product,
Denmark
The Denmark office supports: Faroe Islands, Greenland, Iceland For the rest, it has no sense to reply to you, as you know everything better than anybody else.
Cor
---snip---
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Allen Browne |
last post by:
If you develop for others, you probably have multiple versions of Access
installed so you can edit and create MDEs for clients in different versions.
This works fine under Windows XP, even with...
|
by: Squishy |
last post by:
I tried installing my VS2005 Pro on Vista Ultimate 32 bit RTM today and got
errors stating that VS2005 was not compatible with Vista.
Microsoft......please pull your finger out of my ass and tell...
|
by: =?Utf-8?B?Um9iS2lubmV5MQ==?= |
last post by:
Hello,
We are testing and tweaking some of our software to run on Vista, but it
turns out that we are having problems with one of our programs.
Here is our code:
// attempt an experiment to...
|
by: Viviana Vc |
last post by:
Hi all,
I've read the WindowsVistaUACDevReqs.doc documentation and I have done
different small tests on Vista to understand the bahaviour and now I
have a few questions.
1) If I create a...
|
by: Thomas Thomassen |
last post by:
Hi
I made a screensaver in C# as a test project. At the time of creation I used
XP and everything worked fine.
Then I got a message from someone using Vista about an issue where the
settings...
|
by: Sin Jeong-hun |
last post by:
Since Windows 2000, all user setting files should be stored separately
in the user's application settings directory. But some users still
want all the files to be created in the application folder,...
|
by: star-italia |
last post by:
Hi, I have a big problem:
I am developing a WPF application on Windows Vista SP1 Based on the .NET Framework 3.5 and WPF.
In my application I use a WIndowsFormsHost to (of course) host a...
|
by: idoublepress |
last post by:
Hi all,
I've been struggling with an issue that I hope you can comment on or
provide suggestions to. Our .NET 2.0 (VS2005) based product is
crashing (when the user selects a particular feature on...
|
by: Nick Tatham |
last post by:
I have just purchased a new Dell Windows Vista Home Premium SP1 system.
One of my .NET 2.0 programs doesn't work on it. I have reduced it to the
tiny program below which fails in the same way.
...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| |