VS2005/Vista issues
in [MFC]
|
From: Joseph M. Newcomer on 8 Jun 2007 15:57 I spoke too soon about VS2005 Vista SP1 being more reliable; doing rather trivial single-threaded app debugging, I've managed to crash it six times in the last hour. Each time it seems to crash for a different reason, or at least as the consequence of some completely different action on my part. For those who have been using it, however, I've got a couple questions: It must be run as administrator, which requires an administrator password. What I'd like to do is set myself up to run as a normal user, but with the privileges of running as administrator whenever I want to with only the simple confirmation box (not the need to type in a name and password each time). Any possibility Vista supports something like this? Even though I've run as administrator and sucessfully set the Explorer parameters to never, ever hide anything at all, the VS file dialogs always hide extensions. Or is this just another of the many user-hostile features that Vista now sports? When VS2005 comes back up, it shows the most recent project (I don't yet have "projects", plural). If I click on it, it tells me that it cannot open i:\myclient\projects\test\test.sln, and would I like to remove this from the list. I say 'yes', then I go to file, open, solution, go to the i:\ drive (which is my server), go to myclient\projects, got to i:\myclient\projects\test, see 'test' (not test.sln), click it, and the project opens. So why can it find it from the open dialog but not from the MRU list? Or is this Yet One More VS Bug? The next time it crashes and comes back, the scenario repeats. Another cute feature of Vista: I need to set an environment variable, as user 'flounder'. I can't. I need to run as Administrator. But then I can't change the environment variable for 'flounder', I can only change the environment variable for 'administrator'. Is there a setting that lets a user change his own environment variables? I shouldn't need privileges to change my OWN environment variables! Makes me wonder if any of this stuff had been thought out beforehard, or we have a security-confirmation-as-pixie-dust approach here. (Getting all of Vista installed was the Installer Scenario From Hell, and now that I have it up, the only reason I would ever use it is because I have clients who need Vista support. It is not an operating system suitable for everyday use!) joe Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: David Ching on 8 Jun 2007 21:32 "Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message news:d7cj63l709jops1l9b8cve9gsrcn41hsqi(a)4ax.com... > It must be run as administrator, which requires an administrator password. > What I'd like > to do is set myself up to run as a normal user, but with the privileges of > running as > administrator whenever I want to with only the simple confirmation box > (not the need to > type in a name and password each time). Any possibility Vista supports > something like > this? > Set your Vista account to be an Administrator account (and not a Limited account). Then whenever Admin priviledges are required (that would normally darken the screen and ask for an Admin password), the screen will still darken, but you only have to click the Continue button and not type in a password. Or else disable UAC and have it go back to the WinXP way where no additional steps are required to run anything as true Admin. -- David
From: Joseph M. Newcomer on 9 Jun 2007 00:19 OK. But this will let me normally run with the lower privileges of an ordinary user most of the time, then? I'm still struggling with all this privilege stuff, but I want to be testing in a "normal" user environment most of the time. So I really want the extra step---I've found that I don't need it *all* that often, so I'm trying to create a realistic test environment, but when I need it, I don't want to have to give the password. So I'll do as you suggest. thanks joe On Fri, 8 Jun 2007 18:32:40 -0700, "David Ching" <dc(a)remove-this.dcsoft.com> wrote: >"Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message >news:d7cj63l709jops1l9b8cve9gsrcn41hsqi(a)4ax.com... >> It must be run as administrator, which requires an administrator password. >> What I'd like >> to do is set myself up to run as a normal user, but with the privileges of >> running as >> administrator whenever I want to with only the simple confirmation box >> (not the need to >> type in a name and password each time). Any possibility Vista supports >> something like >> this? >> > >Set your Vista account to be an Administrator account (and not a Limited >account). Then whenever Admin priviledges are required (that would >normally darken the screen and ask for an Admin password), the screen will >still darken, but you only have to click the Continue button and not type in >a password. > >Or else disable UAC and have it go back to the WinXP way where no additional >steps are required to run anything as true Admin. > > >-- 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: David Ching on 9 Jun 2007 00:34 "Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message news:reak63lhj9b6crv83kg4ve912hk1b4nras(a)4ax.com... > OK. But this will let me normally run with the lower privileges of an > ordinary user most > of the time, then? Exactly. In Vista, there's no difference between an Admin user and a Limited user, other than whether you need to provide an Admin password when elevation is required or whether you just need to click Continue. > I'm still struggling with all this privilege stuff, but I want to be > testing in a "normal" user environment most of the time. So I really want > the extra > step---I've found that I don't need it *all* that often, so I'm trying to > create a > realistic test environment, but when I need it, I don't want to have to > give the password. > So I'll do as you suggest. Yeah, this will work perfectly for you. -- David
From: Anthony Wieser on 9 Jun 2007 02:48 I'm successfully running VS2005 sp1 on vista from a limited user account. I think only certain obscure debugging functionality actually requires a full admin account. Anthony Wieser Wieser Software Ltd "Joseph M. Newcomer" <newcomer(a)flounder.com> wrote in message news:d7cj63l709jops1l9b8cve9gsrcn41hsqi(a)4ax.com... >I spoke too soon about VS2005 Vista SP1 being more reliable; doing rather >trivial > single-threaded app debugging, I've managed to crash it six times in the > last hour. Each > time it seems to crash for a different reason, or at least as the > consequence of some > completely different action on my part. > > For those who have been using it, however, I've got a couple questions: > > It must be run as administrator, which requires an administrator password. > What I'd like > to do is set myself up to run as a normal user, but with the privileges of > running as > administrator whenever I want to with only the simple confirmation box > (not the need to > type in a name and password each time). Any possibility Vista supports > something like > this?
|
Next
|
Last
Pages: 1 2 3 4 5 6 7 Prev: Loop for AfxBeginThread Next: afxMapHWND with Shared Release DLL |