F1 for help in VS
-
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
-
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
And you'll never get that 10 minutes back. You're better off using google if you need help. It's faster, and doesn't hog cpu cycles.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
Of all the things wrong with VS, this is at the top of my list. My personal coping strategy: I have set up a macro to take a highlighted word or phrase and throw it at google, prefixed with 'msdn'. Wonder of wonders, I find what I'm looking for, nearly always #1 result. The google search is opened in a window inside VS.
Best wishes, Hans
-
And you'll never get that 10 minutes back. You're better off using google if you need help. It's faster, and doesn't hog cpu cycles.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997I try to avoid F1 but, as I said, I must have some residual muscle memory which occasionally presses it for me
-
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
In ten minutes you may spam well CodeProject, cross posting your question. :rolleyes:
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
I try to avoid F1 but, as I said, I must have some residual muscle memory which occasionally presses it for me
Remove F1 key (I did that with a keyboards "Shutdown" key), or shock yourself anytime you press it.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
Remove F1 key (I did that with a keyboards "Shutdown" key), or shock yourself anytime you press it.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchyBah, that would involve planning for what might happen in the future.
-
And you'll never get that 10 minutes back. You're better off using google if you need help. It's faster, and doesn't hog cpu cycles.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 19975'd, And I'm thinking about creating a second account, just so I can 5-you again...
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
I accidentally press the F1 key sometimes and once the dialog pops up saying its building the help index most of the time I realize that it will be a total waste of time so I cancel, open chrome and google to get actual help.. It's been over a decade since the Visual Studio help has been useful. However I do remember that even back in Visual Studio 6 that if you enabled the sdk help (which you needed for ADO, directX ...) that made your C++ searches favor foxpro answers :mad:
John
-
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
-
And you'll never get that 10 minutes back. You're better off using google if you need help. It's faster, and doesn't hog cpu cycles.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
Some machines I work on I remove the F1 key because I keep accidentally hitting it.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
-
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
I hadn't realised this wound other people up! I replaced it with a macro to Google a while ago. I have written up how as a Tip/Trick and just posted it here: http://www.codeproject.com/Tips/156089/Making-F1-do-something-useful-in-Visual-Studio.aspx[^] But in case it isn't available yet (moderation does take a while, sometimes) the process is: For Visual Studio 2008 and Visual Studio 2010: 1) Open VS, and on the Menu bar select "Tools...Macros...New Macro Project" 2) Call the project "GoogleSearchMSDN" 3) I'm so sorry about this, but VB is involved here. Not my fault, honest! 4) Rename the default Module1 to "DoGoogleSearchMSDN" - right click on the module name in the left hand pan, select "Rename" 5) Enter the following code as the module body:
Sub GoogleSearchMSDN() Dim url As String Dim searchFor As TextSelection = DTE.ActiveDocument.Selection() If searchFor.Text <> "" Then url = "www.google.com/search?q=MSDN+" + searchFor.Text Else url = "www.google.com/search?q=MSDN" End If DTE.ExecuteCommand("View.URL", url) End Sub
- Build and save your module. 7) Use the menu bar again: "Tools...Options...Environment...Keyboard" 8) In the "Show commands containing:" textbox, type "Google" - you should see your new macro. 9) Go to the "Press shortcut keys" box, and press F1 10) Press OK. F1 now searches for "MSDN" plus whatever you highlighted.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
-
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
-
I think I have some residual muscle memory left over from back in the day as I occasionally press F1 in Visual Studio when I need to know something. After waiting 10 minutes for the Help to update itself to reflect changes it takes me to some arcane corner of the MS world which I am sure is fascinating to some people but rarely reflects anything I am interested in.
I never had an issue with it. If you're on some method with the cursor, and press F1, you get the help for that method. Quite convenient.
Wout
-
Remove F1 key (I did that with a keyboards "Shutdown" key), or shock yourself anytime you press it.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchyBut F1 is still often useful in non-MS software.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Yeah, but you go to Google and they yell at you to stop being lazy and go to Code Project's Q&A.
..and water fell from the sky like rain.
THAT was funny (unlike the joke posted above, which was not at all funny).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
I never had an issue with it. If you're on some method with the cursor, and press F1, you get the help for that method. Quite convenient.
Wout
wout de zeeuw wrote:
If you're on some method with the cursor, and press F1, you get the help for that method. Quite convenient.
That is when it gives the correct advice on the technology that you are using. For C++ users it seems to never get it correct. Especially if you have enabled SDK help. Maybe it actually works for .NET users. I do not know because I never rarely use .NET.
John
-
wout de zeeuw wrote:
If you're on some method with the cursor, and press F1, you get the help for that method. Quite convenient.
That is when it gives the correct advice on the technology that you are using. For C++ users it seems to never get it correct. Especially if you have enabled SDK help. Maybe it actually works for .NET users. I do not know because I never rarely use .NET.
John
Aaah, I always wondered why so many people were complaining about the help. It always worked for me perfectly, but in .NET indeed.
Wout
-
I'm glad someone else noticed what a productivity-killer that key is. I always seem to press in at the most inopportune time. I've even thought about physically removing the F1 key from my keyboard.
Good idea. They should have locks so you can prevent certain keys from accidentally being pressed. Or maybe covers to put over keys that prevent them from being pressed.