VS2005/Vista issues
in [MFC]
|
From: Joseph M. Newcomer on 19 Jun 2007 09:07 I was getting conflicting information and wanted to resolve the conflict. joe On Mon, 18 Jun 2007 23:11:16 -0700, "David Ching" <dc(a)remove-this.dcsoft.com> wrote: >"Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message >news:lfge731i9ir7396lr1308kk07b13970e25(a)4ax.com... >> That's what I was trying to determine. Was it correct or not? If it is >> not correct, then >> my solution is simple, as you suggest. > >I don't know why you don't take my word for it, regarding the >SetWindowsHook. I've tried it, and it works exactly I described. If you >want to try the other API's like VirtualAlloc, CreateRemoteThread, etc. then >try it using the SendMessageRemote() function that I offered before, and I >believe you tried on other OS's. > >Myself, I'm not worried about it. I have my Admin account, have UAC >enabled, and that's what I program in. My main dev machine is Vista running >exactly this. > >-- David > Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: Tom Serface on 19 Jun 2007 09:10 Hey David, Thanks for the tip... YES!!! It works. I knew there must be a way to do it and I just never found this dialog yet. I really appreciate your help. :o) Tom "David Ching" <dc(a)remove-this.dcsoft.com> wrote in message news:OwKdi.20427$C96.11956(a)newssvr23.news.prodigy.net... > > Right-click the shortcut (e.g. to DevEnv.exe) and click on Properties. > Click the Shortcut tab. Then click the Advanced button. Check "Run as > administrator." Now everytime you click the shortcut, it will elevate > automatically. > > An Admin account doesn't prompt for a password to elevate. > > If running in an Admin account is suspect, then create another account > called Limited and try your program there before delivering it. That's > what I do and it works great. > > -- David >
From: David Ching on 19 Jun 2007 10:40 "Tom Serface" <tom.nospam(a)camaswood.com> wrote in message news:78269D18-2395-4CA9-A585-DBADDC8D147F(a)microsoft.com... > Hey David, > > Thanks for the tip... YES!!! It works. I knew there must be a way to do > it and I just never found this dialog yet. I really appreciate your help. > > :o) > Sure, glad it works! Thanks also for saying thanks. Not enough of that going around! :-) -- David
From: Joseph M. Newcomer on 20 Jun 2007 10:30 It appears to work, and this is real blessing because I have to restart VS2005 SP1/Vista about every 5 minutes these days (it crashes for no discernable reason, for example, doing such unbelievably complex tasks such as reloading a file that changed outside the VS editor, starting a compilation, breaking in the debugger, single-stepping, etc.). Thanks. joe On Mon, 18 Jun 2007 23:16:14 -0700, "David Ching" <dc(a)remove-this.dcsoft.com> wrote: >"Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message >news:cage73tj26cvekaikuokodvhn3gkag6niq(a)4ax.com... >> Which is exactly the rationale I'm applying. I don't want to deliver a >> product that fails >> in the field once deployed because it ran fine for me as admin, but won't >> work for anyone >> else. >> >> What I want to do is twofold: >> Never, ever have to explicitly run a program "as administrator" if I >> always want >> run it as administrator; double-clicking the icon will ask me if I want >> to elevate, and I will click "continue" or "yes" or "ok" or whatever >> is required >> Never, ever have to supply a password in response to a privilege elevation >> prompt > > >Right-click the shortcut (e.g. to DevEnv.exe) and click on Properties. >Click the Shortcut tab. Then click the Advanced button. Check "Run as >administrator." Now everytime you click the shortcut, it will elevate >automatically. > >An Admin account doesn't prompt for a password to elevate. > >If running in an Admin account is suspect, then create another account >called Limited and try your program there before delivering it. That's what >I do and it works great. > >-- David > Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: SvenC on 20 Jun 2007 10:51
Hi Joe, Joseph M. Newcomer wrote: > It appears to work, and this is real blessing because I have to > restart VS2005 SP1/Vista about every 5 minutes these days (it crashes > for no discernable reason, for example, doing such unbelievably > complex tasks such as reloading a file that changed outside the VS > editor, starting a compilation, breaking in the debugger, > single-stepping, etc.). Thanks. joe Can you describe the term crash a bit more detailed? Does your OS crash/blue screen? Or does a single application crash with something like an access violation? I am running VS2005+SP1+Vista-Update on Vista and Longhorn Beta 3 without any issues. During the Beta of Vista several people complained about blue screens and most of the time they where related to bad memory modules. Vista seems to be more sensible to faulty RAM than XP was. -- SvenC |