|
|
You're in the
dotnet security
group:UAC Issues On Vista
dotnet security:
[quoted text, click to view] "Stephany Young" <noone@localhost> wrote in message news:%23wG32AmrHHA.192@TK2MSFTNGP02.phx.gbl... > Even though I had my roots and highlights redone just a few days ago, I > don't understand why I appear to be having an ongoing blond moment. > > Is it just me or do others among you not 'get' how to make C# and VB.Net > applications play nicely with the the UAC on Vista. > > I have read and reread everything I can find on UAC, 'strong-naming' of > assemblies, 'authenticode signing' of assemblies and, even though I'm not > your average thicko by any means, I just dont get it. http://blogs.msdn.com/cheller/archive/2006/08/24/how-to-embed-a-manifest-in-an-assembly-let-me-count-the-ways.aspx http://www.devx.com/VistaSpecialReport/Article/33856/1954?pf=true
[quoted text, click to view] "Stephany Young" <noone@localhost> wrote in message news:%23n34RemrHHA.1168@TK2MSFTNGP03.phx.gbl... > Thanks for your response Dominick. > > I've got no issues at all with the concept of 'least privilege' or for > that matter being to elevate the privilege of a process or sub-process > when it is absolutely necessary to do so. > > To illustrate my issue, consider an appplication done in VB.Net (for the > sake of argument): > > The project comprises 1 form (Form1) which is > designated as the startup form. > > The form has 1 button with handler for it's > Click event. > > The code in the event handler is simply: > > MessageBox.Show("Hello World!") > > Compile the project resulting in TestApp.exe > > If you 'run' the project in the IDE then no problems at all. The > application behaves as expected. > > Run the project outside the IDE then we are told that an undentified > program (from an unidentified publisher) is attempting to access your > computer. On then need to give assent (for an administrator) or provide an > administrative username/password (for a standard user) before the program > will run. > > How to prepare the application so that it runs without this palaver is the > issue. I just don't get it. I did your example on this Vista Ultimate machine, using a Admin and Standard accounts, ran it from the Bin directory and copied the exe to another directory, even made a desktop short-cut to it, not one time did it ask for permissions to run the exe with giving an Admin user-id and psw, for a Standard account running the program. The laptop came with Vista Home Premium on it using VS 2005 Express, which was upgraded to Vista Ultimate. If the machine has been upgraded with Vista over the top of an existing non Vista O/S like XP, then there is no telling what's happening with Vista.
[quoted text, click to view] "Stephany Young" <noone@localhost> wrote in message news:%23OqXVenrHHA.2240@TK2MSFTNGP03.phx.gbl... > Interesting. You are reporting the same results I get with UAC 'turned > 'off'. I assume that you do have it 'turned on'. Yes UAC is turned on. I made sure that UAC was on, because I had truned on and off at times. It was on for sure both times I did your test example, and it never asked for admin permissions for a Standard user account executing the exe. [quoted text, click to view] > > With over 5000 installs of various Windows versions going right back to NT > 3.51 and Windows 3.1 I have yet to do an 'upgrade-in-place' type install > and I sure as <unlady-like language omitted> aren't going to start those > sort of silly games with Vista. More than 90% of the OS installation > related problems that I have to troubleshoot over the years has been on > 'upgrade-in-place' installations. It's just not worth the hassle. > > See my later post for where I'm up to. > The only other thing it might be is that you have complied this program on an XP machine, and you're trying to run it on Vista. My rule of thumb is build and deploy a program on the platform it's intended to run on to avoid compatibility issues. [quoted text, click to view] >
> "Mr. Arnold" <MR. Arnold@Arnold.com> wrote in message > news:uE$tO8mrHHA.3228@TK2MSFTNGP03.phx.gbl... >> >> "Stephany Young" <noone@localhost> wrote in message >> news:%23n34RemrHHA.1168@TK2MSFTNGP03.phx.gbl... >>> Thanks for your response Dominick. >>> >>> I've got no issues at all with the concept of 'least privilege' or for >>> that matter being to elevate the privilege of a process or sub-process >>> when it is absolutely necessary to do so. >>> >>> To illustrate my issue, consider an appplication done in VB.Net (for the >>> sake of argument): >>> >>> The project comprises 1 form (Form1) which is >>> designated as the startup form. >>> >>> The form has 1 button with handler for it's >>> Click event. >>> >>> The code in the event handler is simply: >>> >>> MessageBox.Show("Hello World!") >>> >>> Compile the project resulting in TestApp.exe >>> >>> If you 'run' the project in the IDE then no problems at all. The >>> application behaves as expected. >>> >>> Run the project outside the IDE then we are told that an undentified >>> program (from an unidentified publisher) is attempting to access your >>> computer. On then need to give assent (for an administrator) or provide >>> an administrative username/password (for a standard user) before the >>> program will run. >>> >>> How to prepare the application so that it runs without this palaver is >>> the issue. I just don't get it. >> >> I did your example on this Vista Ultimate machine, using a Admin and >> Standard accounts, ran it from the Bin directory and copied the exe to >> another directory, even made a desktop short-cut to it, not one time did >> it ask for permissions to run the exe with giving an Admin user-id and >> psw, for a Standard account running the program. >> >> The laptop came with Vista Home Premium on it using VS 2005 Express, >> which was upgraded to Vista Ultimate. >> >> If the machine has been upgraded with Vista over the top of an existing >> non Vista O/S like XP, then there is no telling what's happening with >> Vista. >> >> >> >
[quoted text, click to view] "Stephany Young" <noone@localhost> wrote in message news:uFEf5EorHHA.632@TK2MSFTNGP03.phx.gbl... >I assumed it was turned on but I did to have to ask just in case :) > > Dev Machine = Windows Vista Ultimate > Target Machine = Windows Vista Ultimate > Both machines are members of the same Windows Server 2003 domain. > > The target machine is a fresh install with all updates, joined to the > domain and no other tweaks. > > The users are Domain Admins and Domain users rather than Local Admins and > Local Users. That could explain the difference in behaviour but I would > hope that something as fundamental as that would make no difference. > > I'm not overly concerned that the behaviour that you observed was > different from what I observed because I'm well aware that one can observe > different behaviour on two machines that are ostensibly identical and that > attempting to determine the difference between the two machines is like > attempting to find a needle in a haystack. > Maybe, you need to look at Group Polices for the machine on a domain, put the solution in GAC so that it's trusted, possibly or check what can be done with the .Net Framework Configurations' Runtime Security.
so what exactly is your problem??
Maybe this is helpful: http://www.leastprivilege.com/UACIsForDevelopers.aspx ----- Dominick Baier (http://www.leastprivilege.com) Developing More Secure Microsoft ASP.NET 2.0 Applications (http://www.microsoft.com/mspress/books/9989.asp) [quoted text, click to view] > Even though I had my roots and highlights redone just a few days ago, > I don't understand why I appear to be having an ongoing blond moment. > > Is it just me or do others among you not 'get' how to make C# and > VB.Net applications play nicely with the the UAC on Vista. > > I have read and reread everything I can find on UAC, 'strong-naming' > of assemblies, 'authenticode signing' of assemblies and, even though > I'm not your average thicko by any means, I just dont get it. > > It seems to me that, to some degree it might be a case of "The > Emporer's New Clothes" and nobody is prepared to stand up and say > "Stop! Enough already!". > > If anyone has a blow-by-blow of how to make it work and is prepared to > share their knowledge/experience Then it would be most appreciated. >
have a look at my post - and see if this makes it clearer...
----- Dominick Baier (http://www.leastprivilege.com) Developing More Secure Microsoft ASP.NET 2.0 Applications (http://www.microsoft.com/mspress/books/9989.asp) [quoted text, click to view] > Thanks for your response Dominick. > > I've got no issues at all with the concept of 'least privilege' or for > that matter being to elevate the privilege of a process or sub-process > when it is absolutely necessary to do so. > > To illustrate my issue, consider an appplication done in VB.Net (for > the sake of argument): > > The project comprises 1 form (Form1) which is > designated as the startup form. > The form has 1 button with handler for it's > Click event. > The code in the event handler is simply: > > MessageBox.Show("Hello World!") > > Compile the project resulting in TestApp.exe > > If you 'run' the project in the IDE then no problems at all. The > application behaves as expected. > > Run the project outside the IDE then we are told that an undentified > program (from an unidentified publisher) is attempting to access your > computer. On then need to give assent (for an administrator) or > provide an administrative username/password (for a standard user) > before the program will run. > > How to prepare the application so that it runs without this palaver is > the issue. I just don't get it. > > "Dominick Baier" <dbaier@pleasepleasenospam_leastprivilege.com> wrote > in message news:51eb304811c9e8c97c824f02d620@news.microsoft.com... > >> so what exactly is your problem?? >> >> Maybe this is helpful: >> >> http://www.leastprivilege.com/UACIsForDevelopers.aspx >> >> ----- >> Dominick Baier (http://www.leastprivilege.com) >> Developing More Secure Microsoft ASP.NET 2.0 Applications >> (http://www.microsoft.com/mspress/books/9989.asp) >> >>> Even though I had my roots and highlights redone just a few days >>> ago, I don't understand why I appear to be having an ongoing blond >>> moment. >>> >>> Is it just me or do others among you not 'get' how to make C# and >>> VB.Net applications play nicely with the the UAC on Vista. >>> >>> I have read and reread everything I can find on UAC, 'strong-naming' >>> of assemblies, 'authenticode signing' of assemblies and, even though >>> I'm not your average thicko by any means, I just dont get it. >>> >>> It seems to me that, to some degree it might be a case of "The >>> Emporer's New Clothes" and nobody is prepared to stand up and say >>> "Stop! Enough already!". >>> >>> If anyone has a blow-by-blow of how to make it work and is prepared >>> to share their knowledge/experience Then it would be most >>> appreciated. >>>
[quoted text, click to view]
"Stephany Young" <noone@localhost> wrote in message news:%23wG32AmrHHA.192@TK2MSFTNGP02.phx.gbl... > Even though I had my roots and highlights redone just a few days ago, I > don't understand why I appear to be having an ongoing blond moment. > > Is it just me or do others among you not 'get' how to make C# and VB.Net > applications play nicely with the the UAC on Vista. > > I have read and reread everything I can find on UAC, 'strong-naming' of > assemblies, 'authenticode signing' of assemblies and, even though I'm not > your average thicko by any means, I just dont get it. > > It seems to me that, to some degree it might be a case of "The Emporer's > New Clothes" and nobody is prepared to stand up and say "Stop! Enough > already!". > > If anyone has a blow-by-blow of how to make it work and is prepared to > share their knowledge/experience Then it would be most appreciated. > > How do your UAC settings look like? You can check this by running "Local Security Policy" from "Administrative Tools" I had the same issues when running beta's and RC's of Vista before, but I never had this issue on Vista RTM, running C# applications (if that matters at all) as standard user. Also, make sure you have VS2005 SP1 http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx and VS2005 SP1 http://support.microsoft.com/kb/929470 installed? Willy.
[quoted text, click to view]
"Stephany Young" <noone@localhost> wrote in message news:O8gJbHorHHA.532@TK2MSFTNGP06.phx.gbl... > Thanks Willy. > > Been there and even got the tee-shirt for those two updates :) > > The UAC setting are 'out-of-the-box'. Absolutely NO tweaks to the target > machine except for applying all the updates and joining a domain. > UAC settings may differ when Domain policies apply! Do you run this application with full "administrator" privileges? For instance by Right clicking in Explorer and "Run As Administrator" ? Also, check the .exe properties -> Compatibility -> Privilege Level - "Run this program as an administrator". If this option is enabled then you will always get the UAC prompt. Your application is not signed and does not have a UAC manifest included, so, somehow it's forced to "run as administrator", hence the UAC prompt. Willy.
Even though I had my roots and highlights redone just a few days ago, I
don't understand why I appear to be having an ongoing blond moment. Is it just me or do others among you not 'get' how to make C# and VB.Net applications play nicely with the the UAC on Vista. I have read and reread everything I can find on UAC, 'strong-naming' of assemblies, 'authenticode signing' of assemblies and, even though I'm not your average thicko by any means, I just dont get it. It seems to me that, to some degree it might be a case of "The Emporer's New Clothes" and nobody is prepared to stand up and say "Stop! Enough already!". If anyone has a blow-by-blow of how to make it work and is prepared to share their knowledge/experience Then it would be most appreciated.
Thanks for your response Dominick.
I've got no issues at all with the concept of 'least privilege' or for that matter being to elevate the privilege of a process or sub-process when it is absolutely necessary to do so. To illustrate my issue, consider an appplication done in VB.Net (for the sake of argument): The project comprises 1 form (Form1) which is designated as the startup form. The form has 1 button with handler for it's Click event. The code in the event handler is simply: MessageBox.Show("Hello World!") Compile the project resulting in TestApp.exe If you 'run' the project in the IDE then no problems at all. The application behaves as expected. Run the project outside the IDE then we are told that an undentified program (from an unidentified publisher) is attempting to access your computer. On then need to give assent (for an administrator) or provide an administrative username/password (for a standard user) before the program will run. How to prepare the application so that it runs without this palaver is the issue. I just don't get it. "Dominick Baier" <dbaier@pleasepleasenospam_leastprivilege.com> wrote in message news:51eb304811c9e8c97c824f02d620@news.microsoft.com... [quoted text, click to view] > so what exactly is your problem??
> > Maybe this is helpful: > > http://www.leastprivilege.com/UACIsForDevelopers.aspx > > ----- > Dominick Baier (http://www.leastprivilege.com) > > Developing More Secure Microsoft ASP.NET 2.0 Applications > (http://www.microsoft.com/mspress/books/9989.asp) > >> Even though I had my roots and highlights redone just a few days ago, >> I don't understand why I appear to be having an ongoing blond moment. >> >> Is it just me or do others among you not 'get' how to make C# and >> VB.Net applications play nicely with the the UAC on Vista. >> >> I have read and reread everything I can find on UAC, 'strong-naming' >> of assemblies, 'authenticode signing' of assemblies and, even though >> I'm not your average thicko by any means, I just dont get it. >> >> It seems to me that, to some degree it might be a case of "The >> Emporer's New Clothes" and nobody is prepared to stand up and say >> "Stop! Enough already!". >> >> If anyone has a blow-by-blow of how to make it work and is prepared to >> share their knowledge/experience Then it would be most appreciated. >> > >
Interesting. You are reporting the same results I get with UAC 'turned
'off'. I assume that you do have it 'turned on'. With over 5000 installs of various Windows versions going right back to NT 3.51 and Windows 3.1 I have yet to do an 'upgrade-in-place' type install and I sure as <unlady-like language omitted> aren't going to start those sort of silly games with Vista. More than 90% of the OS installation related problems that I have to troubleshoot over the years has been on 'upgrade-in-place' installations. It's just not worth the hassle. See my later post for where I'm up to. [quoted text, click to view] "Mr. Arnold" <MR. Arnold@Arnold.com> wrote in message
news:uE$tO8mrHHA.3228@TK2MSFTNGP03.phx.gbl... > > "Stephany Young" <noone@localhost> wrote in message > news:%23n34RemrHHA.1168@TK2MSFTNGP03.phx.gbl... >> Thanks for your response Dominick. >> >> I've got no issues at all with the concept of 'least privilege' or for >> that matter being to elevate the privilege of a process or sub-process >> when it is absolutely necessary to do so. >> >> To illustrate my issue, consider an appplication done in VB.Net (for the >> sake of argument): >> >> The project comprises 1 form (Form1) which is >> designated as the startup form. >> >> The form has 1 button with handler for it's >> Click event. >> >> The code in the event handler is simply: >> >> MessageBox.Show("Hello World!") >> >> Compile the project resulting in TestApp.exe >> >> If you 'run' the project in the IDE then no problems at all. The >> application behaves as expected. >> >> Run the project outside the IDE then we are told that an undentified >> program (from an unidentified publisher) is attempting to access your >> computer. On then need to give assent (for an administrator) or provide >> an administrative username/password (for a standard user) before the >> program will run. >> >> How to prepare the application so that it runs without this palaver is >> the issue. I just don't get it. > > I did your example on this Vista Ultimate machine, using a Admin and > Standard accounts, ran it from the Bin directory and copied the exe to > another directory, even made a desktop short-cut to it, not one time did > it ask for permissions to run the exe with giving an Admin user-id and > psw, for a Standard account running the program. > > The laptop came with Vista Home Premium on it using VS 2005 Express, which > was upgraded to Vista Ultimate. > > If the machine has been upgraded with Vista over the top of an existing > non Vista O/S like XP, then there is no telling what's happening with > Vista. > > >
Thank you both Dominick and Mr Arnold.
The content of the links you supplied filled in some of the gaps in my understanding of how to embed manifests. I found that some of the articles would explain one part very well but gloss over the detail of another part but another article would flesh the 'missing' part out. I'm not criticising the writers because I know how easy it is to assume that the reader already knows what your'e talking about. The upshot is that, when you combine the pertinent bits from the various articles, it all becomes clear. One bit that has me perplexed though is that compiling a manifest as a resource in the prebuild event using C# is fine but when running rc.exe in a batch file it spits is dummy and thows an RC2135 error on one of the #define statements - scary. Anyway, I now have a managable kludge that will allow me to embed a manifest in a VB.Net project that will have to do me until whatever Orcas is going to finally be called goes RTM. [quoted text, click to view] "Stephany Young" <noone@localhost> wrote in message
news:%23wG32AmrHHA.192@TK2MSFTNGP02.phx.gbl... > Even though I had my roots and highlights redone just a few days ago, I > don't understand why I appear to be having an ongoing blond moment. > > Is it just me or do others among you not 'get' how to make C# and VB.Net > applications play nicely with the the UAC on Vista. > > I have read and reread everything I can find on UAC, 'strong-naming' of > assemblies, 'authenticode signing' of assemblies and, even though I'm not > your average thicko by any means, I just dont get it. > > It seems to me that, to some degree it might be a case of "The Emporer's > New Clothes" and nobody is prepared to stand up and say "Stop! Enough > already!". > > If anyone has a blow-by-blow of how to make it work and is prepared to > share their knowledge/experience Then it would be most appreciated. > >
I assumed it was turned on but I did to have to ask just in case :)
Dev Machine = Windows Vista Ultimate Target Machine = Windows Vista Ultimate Both machines are members of the same Windows Server 2003 domain. The target machine is a fresh install with all updates, joined to the domain and no other tweaks. The users are Domain Admins and Domain users rather than Local Admins and Local Users. That could explain the difference in behaviour but I would hope that something as fundamental as that would make no difference. I'm not overly concerned that the behaviour that you observed was different from what I observed because I'm well aware that one can observe different behaviour on two machines that are ostensibly identical and that attempting to determine the difference between the two machines is like attempting to find a needle in a haystack. [quoted text, click to view] "Mr. Arnold" <MR. Arnold@Arnold.com> wrote in message
news:OQ4uO2nrHHA.1476@TK2MSFTNGP06.phx.gbl... > > "Stephany Young" <noone@localhost> wrote in message > news:%23OqXVenrHHA.2240@TK2MSFTNGP03.phx.gbl... >> Interesting. You are reporting the same results I get with UAC 'turned >> 'off'. I assume that you do have it 'turned on'. > > Yes UAC is turned on. I made sure that UAC was on, because I had truned on > and off at times. It was on for sure both times I did your test example, > and it never asked for admin permissions for a Standard user account > executing the exe. > >> >> With over 5000 installs of various Windows versions going right back to >> NT 3.51 and Windows 3.1 I have yet to do an 'upgrade-in-place' type >> install and I sure as <unlady-like language omitted> aren't going to >> start those sort of silly games with Vista. More than 90% of the OS >> installation related problems that I have to troubleshoot over the years >> has been on 'upgrade-in-place' installations. It's just not worth the >> hassle. >> >> See my later post for where I'm up to. >> > > The only other thing it might be is that you have complied this program on > an XP machine, and you're trying to run it on Vista. > > My rule of thumb is build and deploy a program on the platform it's > intended to run on to avoid compatibility issues. > >> >> "Mr. Arnold" <MR. Arnold@Arnold.com> wrote in message >> news:uE$tO8mrHHA.3228@TK2MSFTNGP03.phx.gbl... >>> >>> "Stephany Young" <noone@localhost> wrote in message >>> news:%23n34RemrHHA.1168@TK2MSFTNGP03.phx.gbl... >>>> Thanks for your response Dominick. >>>> >>>> I've got no issues at all with the concept of 'least privilege' or for >>>> that matter being to elevate the privilege of a process or sub-process >>>> when it is absolutely necessary to do so. >>>> >>>> To illustrate my issue, consider an appplication done in VB.Net (for >>>> the sake of argument): >>>> >>>> The project comprises 1 form (Form1) which is >>>> designated as the startup form. >>>> >>>> The form has 1 button with handler for it's >>>> Click event. >>>> >>>> The code in the event handler is simply: >>>> >>>> MessageBox.Show("Hello World!") >>>> >>>> Compile the project resulting in TestApp.exe >>>> >>>> If you 'run' the project in the IDE then no problems at all. The >>>> application behaves as expected. >>>> >>>> Run the project outside the IDE then we are told that an undentified >>>> program (from an unidentified publisher) is attempting to access your >>>> computer. On then need to give assent (for an administrator) or provide >>>> an administrative username/password (for a standard user) before the >>>> program will run. >>>> >>>> How to prepare the application so that it runs without this palaver is >>>> the issue. I just don't get it. >>> >>> I did your example on this Vista Ultimate machine, using a Admin and >>> Standard accounts, ran it from the Bin directory and copied the exe to >>> another directory, even made a desktop short-cut to it, not one time did >>> it ask for permissions to run the exe with giving an Admin user-id and >>> psw, for a Standard account running the program. >>> >>> The laptop came with Vista Home Premium on it using VS 2005 Express, >>> which was upgraded to Vista Ultimate. >>> >>> If the machine has been upgraded with Vista over the top of an existing >>> non Vista O/S like XP, then there is no telling what's happening with >>> Vista. >>> >>> >>> >> >
Thanks Willy.
Been there and even got the tee-shirt for those two updates :) The UAC setting are 'out-of-the-box'. Absolutely NO tweaks to the target machine except for applying all the updates and joining a domain. [quoted text, click to view] "Willy Denoyette [MVP]" <willy.denoyette@telenet.be> wrote in message
news:OD$uY2nrHHA.5032@TK2MSFTNGP04.phx.gbl... > "Stephany Young" <noone@localhost> wrote in message > news:%23wG32AmrHHA.192@TK2MSFTNGP02.phx.gbl... >> Even though I had my roots and highlights redone just a few days ago, I >> don't understand why I appear to be having an ongoing blond moment. >> >> Is it just me or do others among you not 'get' how to make C# and VB.Net >> applications play nicely with the the UAC on Vista. >> >> I have read and reread everything I can find on UAC, 'strong-naming' of >> assemblies, 'authenticode signing' of assemblies and, even though I'm not >> your average thicko by any means, I just dont get it. >> >> It seems to me that, to some degree it might be a case of "The Emporer's >> New Clothes" and nobody is prepared to stand up and say "Stop! Enough >> already!". >> >> If anyone has a blow-by-blow of how to make it work and is prepared to >> share their knowledge/experience Then it would be most appreciated. >> >> > > > > How do your UAC settings look like? You can check this by running "Local > Security Policy" from "Administrative Tools" > I had the same issues when running beta's and RC's of Vista before, but I > never had this issue on Vista RTM, running C# applications (if that > matters at all) as standard user. > Also, make sure you have VS2005 SP1 > http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx and VS2005 SP1 > http://support.microsoft.com/kb/929470 installed? > > Willy. >
Thanks again Willy.
Me issues were not really to do with the behaviour of UAC, rather they were to do not being to come to grips with how to make an application 'play nicely' with UAC. After extensive research, the methodolgy still seemed a bit on the esoteric side, however, with another couple of pieces falling into place as a result of response to my OP it is now a lot clearer and I now have apps with imbedded manifests that enable them to 'play nicely' with UAC. It's all part of the ever-continuing learning curve, but when you don't know the answer the question is always hard. [quoted text, click to view] "Willy Denoyette [MVP]" <willy.denoyette@telenet.be> wrote in message
news:u0aDyeorHHA.1212@TK2MSFTNGP05.phx.gbl... > "Stephany Young" <noone@localhost> wrote in message > news:O8gJbHorHHA.532@TK2MSFTNGP06.phx.gbl... >> Thanks Willy. >> >> Been there and even got the tee-shirt for those two updates :) >> >> The UAC setting are 'out-of-the-box'. Absolutely NO tweaks to the target >> machine except for applying all the updates and joining a domain. >> > > UAC settings may differ when Domain policies apply! > Do you run this application with full "administrator" privileges? For > instance by Right clicking in Explorer and "Run As Administrator" ? Also, > check the .exe properties -> Compatibility -> Privilege Level - "Run this > program as an administrator". If this option is enabled then you will > always get the UAC prompt. > Your application is not signed and does not have a UAC manifest included, > so, somehow it's forced to "run as administrator", hence the UAC prompt. > > Willy. >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |