[RESOLVED] Windows 7 recent project list empty

[dilettante]

Although, Tyson said in post #3 that he installed Visual Basic 6.0 under the administrator account. If that is the case he shouldn't have to do "Run as administrator" when he wants to use Visual Basic 6.0.

Not true. It must always run as admin or else it can cause registry problems. During its use the VB6 IDE and compiler register referenced components and new components you create. Running w/o elevation lots of junky virtualized registry entries get made and the resulting programs can have issues. The IDE also needs the Debugger right when working with DCOM components.

Back in 2006 during the "Longhorn" developer info transfers and Vista beta programs Microsoft made all of that very clear. The main issue was the removal of the "Power User" security role from Windows. In XP and Win2K VB6 developers needed to be Power Users, though Joe Homeboy tended to just run logged on with an admin account.

Just run it elevated and avoid "mysterious" problems.

[Nightwalker83]

Not true. It must always run as admin or else it can cause registry problems. During its use the VB6 IDE and compiler register referenced components and new components you create. Running w/o elevation lots of junky virtualized registry entries get made and the resulting programs can have issues. The IDE also needs the Debugger right when working with DCOM components.

Interesting! Regardless of whether or not I run VB6 on Windows 7 with run as admin it still comes up with configuration for Visual Studios 2010. Although, I think that is because I have both installed on my laptop and Win7 start the newer version which is VS 2010 by default.

Edit:

In my honest opinion running any program using "Run As Administrator" when you have already installed the program as the administrator and are logged in as an admin to the system is a joke.

[dilettante]

In my honest opinion running any program using "Run As Administrator" when you have already installed the program as the administrator and are logged in as an admin to the system is a joke.

Well the alternative is for VB6 to jump through hoops and raise elevation prompts whenever it needed to do things requiring changes to system state or cross-context debugging. Even so that would mean changing VB6.exe and Microsoft isn't likely to do that.

The truth is that later Visual Studio versions (.Net, C++, whatever) are also supposed to be run elevated every time for the same reasons. The Express editions are crippled enough that this is seldom a problem for them though.

People just don't read the info Microsoft puts out I guess. Here's an oldie from when Vista came out:

Visual Studio 2005 on Windows Vista Issue List (Admin)

It was not reissued for Windows 7 because (a.) Windows 7 is a minor update and (b.) developers were all supposed to pay attention to the Longhorn developer guidance back in 2006 - 2007. You snooze, you lose.

[Nightwalker83]

It was not reissued for Windows 7 because (a.) Windows 7 is a minor update and (b.) developers were all supposed to pay attention to the Longhorn developer guidance back in 2006 - 2007. You snooze, you lose.

Honestly, who is going to right-click the program icon/shortcut every single time when they can just double (left button) click? It is a wonder Microsoft didn't put "Run As Administrator" as the default run program option.