Who moved the Start Page?
-
Kevin Marois wrote:
Should't the option to Compile be the same regardless of version?
But it is: it's F5, and it always has been, in every version of Visual Studio I can remember, at least since "Visual Studio .NET" in 2002. :confused: EDIT: Correction - F5 is
Debug.Start.Build.Compileis Ctrl+F7, andBuild.BuildSolutionis Ctrl+Shift+B. Default Keyboard Shortcuts in Visual Studio | Microsoft Docs[^] The VS2012 version of the documentation[^] shows how the mapping (used to?) differ depending on which scheme you selected when you first started Visual Studio.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
For you it is. It's F6 on my Home PC and both my work PC's. And the other Dev's here say the same. That right there is my point. It should be the same for ALL Visual Studio installations everywhere.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
For you it is. It's F6 on my Home PC and both my work PC's. And the other Dev's here say the same. That right there is my point. It should be the same for ALL Visual Studio installations everywhere.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Kevin Marois wrote:
It should be the same for ALL Visual Studio installations everywhere.
But then you'll get people complaining that they can't customise the shortcuts, and the default isn't the key they want to use. :laugh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Kevin Marois wrote:
It should be the same for ALL Visual Studio installations everywhere.
But then you'll get people complaining that they can't customise the shortcuts, and the default isn't the key they want to use. :laugh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Agreed. And I have no problem with allowing customization... But out of the box it should be the same.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Agreed. And I have no problem with allowing customization... But out of the box it should be the same.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Well, according to Microsoft, it is:
Default Keyboard Shortcuts in Visual Studio[^]:
Debug.Restart: Ctrl+Shift+F5 Debug.Start: F5 Debug.StartWithoutDebugging: Ctrl+F5 Debug.StopDebugging: Shift+F5
Have you picked a different keyboard mapping scheme?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Well, according to Microsoft, it is:
Default Keyboard Shortcuts in Visual Studio[^]:
Debug.Restart: Ctrl+Shift+F5 Debug.Start: F5 Debug.StartWithoutDebugging: Ctrl+F5 Debug.StopDebugging: Shift+F5
Have you picked a different keyboard mapping scheme?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I've never changed it on any installation
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I've never changed it on any installation
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
That would be a hysterical GPO, just to mess with the devs.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
That would be a hysterical GPO, just to mess with the devs.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
Well, it's working
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I've never changed it on any installation
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
You should probably report it to Microsoft as a bug, then. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
In VS2017, prior to 15.2, Start Page was under the View menu. Now its under the File menu. I don't want to File the Start Page, I want to view it.
"Time flies like an arrow. Fruit flies like a banana."
Tools > Customize Just sayin'.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
Well, according to Microsoft, it is:
Default Keyboard Shortcuts in Visual Studio[^]:
Debug.Restart: Ctrl+Shift+F5 Debug.Start: F5 Debug.StartWithoutDebugging: Ctrl+F5 Debug.StopDebugging: Shift+F5
Have you picked a different keyboard mapping scheme?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Here's another great change - at least in my VS installations... Create a class and add an interface (eg ": IMyInterface").. Used to be you could Right Click on the interface name and choose Implement Interface. Now, you have highlight the interface name and choose "CTRL+." - ya, that's intuitive. In VS2017 (Maybe 15 too) a dialog opens which is fine, but the control to open it went from RC'ing to "CTRL+." I mean, really?????
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Tools > Customize Just sayin'.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
The point here is that for default installations both Richard and I are seeing different defaults.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Here's another great change - at least in my VS installations... Create a class and add an interface (eg ": IMyInterface").. Used to be you could Right Click on the interface name and choose Implement Interface. Now, you have highlight the interface name and choose "CTRL+." - ya, that's intuitive. In VS2017 (Maybe 15 too) a dialog opens which is fine, but the control to open it went from RC'ing to "CTRL+." I mean, really?????
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I use R#, so it's always Alt+Enter. :D I guess they switched to Ctrl+. when they moved to Roslyn (VS2015), and dramatically increased the number of built-in refactorings.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Well, according to Microsoft, it is:
Default Keyboard Shortcuts in Visual Studio[^]:
Debug.Restart: Ctrl+Shift+F5 Debug.Start: F5 Debug.StartWithoutDebugging: Ctrl+F5 Debug.StopDebugging: Shift+F5
Have you picked a different keyboard mapping scheme?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
They are talking about compiling not debug. I have VS 2012 and Build Solution is F7 and Compile is Ctrl-F7.
-
They are talking about compiling not debug. I have VS 2012 and Build Solution is F7 and Compile is Ctrl-F7.
Compile. And you just proved my point. Where did F7 come from???
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
The point here is that for default installations both Richard and I are seeing different defaults.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Maybe it differs from US to UK keyboards?
In this present crisis, government is not the solution to our problem; government is the problem. ~ Ronald Reagan
Could be, because the Brit's say "F5" and "F6" differently than us yanks ;P ;P ;P
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Richard Deeming wrote:
It's always been F5 for me. And Ctrl+Shift+F5 is bound to the "Debug.Restart" command.
Well you just validated my grievance. Should't the option to Compile be the same regardless of version?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Kevin Marois wrote:
Should't the option to Compile be the same regardless of version?
When you first start up Visual Studio it asks what settings you want to use, C#, VB.Net, etc. That will initially set your shortcut keys as well.
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
-
Kevin Marois wrote:
Should't the option to Compile be the same regardless of version?
But it is: it's F5, and it always has been, in every version of Visual Studio I can remember, at least since "Visual Studio .NET" in 2002. :confused: EDIT: Correction - F5 is
Debug.Start.Build.Compileis Ctrl+F7, andBuild.BuildSolutionis Ctrl+Shift+B. Default Keyboard Shortcuts in Visual Studio | Microsoft Docs[^] The VS2012 version of the documentation[^] shows how the mapping (used to?) differ depending on which scheme you selected when you first started Visual Studio.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Kevin Marois wrote:
Should't the option to Compile be the same regardless of version?
But it is: it's F5, and it always has been, in every version of Visual Studio I can remember, at least since "Visual Studio .NET" in 2002. :confused: EDIT: Correction - F5 is
Debug.Start.Build.Compileis Ctrl+F7, andBuild.BuildSolutionis Ctrl+Shift+B. Default Keyboard Shortcuts in Visual Studio | Microsoft Docs[^] The VS2012 version of the documentation[^] shows how the mapping (used to?) differ depending on which scheme you selected when you first started Visual Studio.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
For you it is. It's F6 on my Home PC and both my work PC's. And the other Dev's here say the same. That right there is my point. It should be the same for ALL Visual Studio installations everywhere.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
