Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Strange Windows 7 Problem

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
jmatthias Posted - Feb 03 2010 : 10:33:27 PM
Using Windows 7, once you have a running application in the taskbar, you can start a new instance of the application by either right clicking on the taskbar button and selecting the name of the application from the menu or you can hold the shift key down and click the taskbar button.

I am using VAX with VS.NET 2008. If I right click on the VS.NET taskbar button and launch a new instance, VAX is loaded correctly into VS.NET. However, if I shift click the taskbar button, VAX does not load into VS.NET 2008!

You would assume that both methods of starting a new instance of VS.NET would result in the same result. But for some reason it does not.

Joel
2   L A T E S T    R E P L I E S    (Newest First)
accord Posted - Feb 04 2010 : 03:48:57 AM
One more way to start new instance of VS (or any other program) in Win7 is to middle click. It does the same as shift or the mentioned context menu item.
jmatthias Posted - Feb 03 2010 : 10:49:50 PM
I think I know this answer to my problem. I think VS.NET itself checks to see if the shift key is pressed when it starts up and if it is, it does not load add-ins. I guess the shift key is a safe mode trigger.

I tested it by using the right click method of starting a new instance and at the same time I held the shift key. This instance did not load VAX.

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000