How to prevent the Visual Studio window arrangement from changing every time you breathe?
Productivity tricks in Visual Studio
11–20 of 25 posts
Re: Productivity tricks in Visual Studio
#12How to prevent the Visual Studio window arrangement from changing every time you breathe?
You can save the window arrangement, and restore it with a key chord.
Re: Productivity tricks in Visual Studio
#13I'd been using Visual Studio for quite a while before I discovered it supported something like Vim's visual block mode - you can use alt-shift to select (and then edit) blocks of text.
I highly recommend VsVim[0] if you're a vim user. It's very lightweight and complete, it persists your register contents, shows you visual block ranges on the left side, supports macros, and it plays well with intellisense.
0. https://marketplace.visualstudio.com/items?itemName=JaredPar...
Re: Productivity tricks in Visual Studio
#14As F1 is pretty obvious I'll list some other obvious ones:
Right-click on something, choose 'go to definition' - see the code for that method or whatever. When you're done, the 'back' button in the toolbar can take you back. Also F12 and Alt-F12 do same/similar
Highlight a method or class name, right-click, choose Rename - will allow you to rename it and then will also rename all references to it
Right-click a block of code, choose 'quick actions and refactorings', then 'extract method'. It will pull out the code, figure out the parameters and create a new method for you.
Re: Productivity tricks in Visual Studio
#15I'd been using Visual Studio for quite a while before I discovered it supported something like Vim's visual block mode - you can use alt-shift to select (and then edit) blocks of text.
It also mimics vim mode with a plugin
Re: Productivity tricks in Visual Studio
#16Type "prop" then tab to create a property.
The back arrow is useful too but on VS 2017 I believe they added the Peek Definition so you don't need to go out of the original file you're checking.
Re: Productivity tricks in Visual Studio
#17JetBrains Rider is a significant productivity upgrade to Visual Studio, especially when working with a large solution.
The problem is that Rider doesn't have some features that are a must-have for me, like Edit and Continue, Immediate Window, Docker-Compose debugger and some others.
Besides that, I love the performance.
Re: Productivity tricks in Visual Studio
#18As F1 is pretty obvious I'll list some other obvious ones: Right-click on something, choose 'go to definition' - see the code for that method or whatever. When you're done, the 'back' button in the toolbar can take you back. Also F12 and Alt-F12 do same/similar Highlight a method or class name, right-click, choose Rename - will allow you to rename it and then will also rename all references to it Right-click a block…
> Rename - will allow you to rename it and then will also rename all references to it
Ctrl + r + r (twice in a row) is the shortcut for this, super useful
Re: Productivity tricks in Visual Studio
#19CTRL+F search for a word then hit ALT+Enter to select all with a multi-cursor.
Re: Productivity tricks in Visual Studio
#20It’s a little opposite of the topic, but am I the only one who’s noticed a considerable downturn in the productivity of VS? Yesterday I wanted to import “Microsoft System Center Orchestrator Web Service” in a C# project, something which used to be a simple “add service reference”, only to be greeted by “we don’t import ODATA services this way anymore...” message and sent to some obscure framework for it. The first fr…
Visual Studio anti-productivity feature: if you want to turn "convert warnings to errors" on, or change .NET framework level, in a large C# solution, you have to do it in each individual project. By hand or by writing a program to rewrite the XML.
The whole "project" paradigm seems to have always been a little bit broken, rather than just having a clearer "sources" and "targets" definition.