Enhancing Visual Studio

In recent months, I’ve been working exclusively with Visual Studio. This is something I tried to avoid for years after some bad experiences with earlier iterations, however, the latests releases have constantly improved on what made it good in the first place and working with it is now a pleasure.

Being a vim maniac and a bit of configuration freak I had some changes to do to make it even greater. I’ll try to collect and update my Visual Studio configuration tips and plugins in this article.

ViEmu

If you want the Vim experience with the perks of Visual Studio, there are two ways to go about it: VsVim or ViEmu.

Now while VsVim is free and open source, I do feel that it looks a bit unpolished and rough around the edges. You don’t have to take my word for it as you can try out ViEmu for free for 30 days. If I knew the first thing about Visual Studio plugin programming, I’d help make VsVim better, but as I don’t have much free time anymore, ViEmu looked to me like a better choice despite its steep pricing.

One great thing that both ViEmu and VsVim provide is a partial support of .vimrc-like configuration. It doesn’t have all the cool features the standard .vimrc allows you to do, but it certainly allows for some useful adjustments. Here’s my .viemurc; it can even be used with ViEmu’s trial version:

" Replace all occurrences by default
set gdefault

" Clear highlights
nnoremap ;<space> :noh<cr>

" Maps the % (go to corresponding bracket) to ù
nnoremap ù %
vnoremap ù %

" Make the indent behaviour a little more sane
vmap <Tab> >gv
vmap <S-Tab> <gv

" Visual shifting (does not exit Visual mode)
vnoremap < <gv
vnoremap > >gv

" Enable ctrl+h and ctrl+l to move around the buffers
nmap <c-l> :bn<CR>
nmap <c-h> :bp<CR>

" start replacing the word under the cursor in the current scope
nnoremap ;s "zyiw<esc>[{V]}:s/<c-r>z/

To use it, it must be saved as “.viemurc” in your user folder (“%USERPROFILE%”).

Line Endings Unifiers

The Unity3D Editor often complains when it encounters inconsistent line endings, a way to unify the line endings of your source files is a good way to clear your console from useless warnings getting in the way of your useful debug messages.

The Line Endings Unifiers plugin is a great to do just that.

Installing it is not enough though. You have to configure it before being finally ready to work.

The future?

I’ll try to keep this article updated with other plugins and configurations I find useful in the future.



Enter your desired user name/password and after your comment has been reviewed by an admin it will be posted and your account will be enabled. If you are already registered please login before posting.