|
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."
|
|
|
|
|
I hear ya. That is one of my biggest gripes with MS. FFS STOP MOVING THINGS AROUND!!!
One that REALLLLLLLLLY bugs me is they change the keyboard shortcuts to compile. In VS2016 it was F6, then in 2015 it was CTRL+SHITF+F6 something else, now in my version 2017 it's back to F6.
As far as the Start Page... I hear a lot of ppl say they disable it. I can't understand why. If the feeds are too slow then turn them off, but the MRU list and Project Options are useful.
And, in 2010 MS provided a WPF Start Page template which MS hasn't upgraded since. I once created a really useful start page but I can't now upgrade it.
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: VS2016
I must have missed that version! 
Kevin Marois wrote: F6
It's always been F5 for me. And Ctrl+Shift+F5 is bound to the "Debug.Restart" command.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
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?
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. 
EDIT: Correction - F5 is Debug.Start.
Build.Compile is Ctrl+F7, and Build.BuildSolution is 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
modified 18-May-17 10:55am.
|
|
|
|
|
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.
"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.
|
|
|
|
|
Well, according to Microsoft, it is:
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.
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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. 
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
|
|
|
|
|
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.
|
|
|
|
|
Build Solution is Ctrl+Shift+B in 2015 and 2017 for me.
Check your "Additional Keyboard mapping scheme" option under Options/Environment/Keyboard.
If I have Visual C# 2005 selected it adds F6
If I have Visual C++ 2 selected it adds Shift+F8
Visual C++ 6 adds F7
|
|
|
|
|
No it's F7. F6 is for switching Windows.
|
|
|
|
|
Whether or not you're debugging:
F6 - compile
F5 - compile and run
I hit F6 often - don't always need to run but I do it just to save files and make sure I didn't miss something that won't compile.
|
|
|
|
|
That's Build & Run.
I think he wants to just build it, and then go home without seeing if it actually works.
|
|
|
|
|
Where did you get that from? F5 has always been "start with debugging", Ctrl+F5 "start without debugging. F6 switch windows, F7 Compile, build etc.
|
|
|
|
|
F5 is Run over here. F6 is Build. I've bound SHIFT+F6 to ReBuild.
|
|
|
|
|
Except for me it's F7 build ctrl-F7 compile F5 - run, and has been since before the millenium. F10 step over, F11 step in ... you get the drill
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
