Skip to main content

Oneway ticket from Visual Studio to Vim

Image
By
Not so while ago If you had asked: Would you ever leave Visual Studio (+ReSharper and tools)?. The answer would be: “Hell No!, Why on earth I'll leave the most powerful IDE ever built?!

But as the time goes by, I've changed my mind...
Lately I been working on Mac, Linux and Windows, doing .NET, JavaScript, TypeScript, Ruby, HTML, CSS, some SQL and batch/shell scripts. Having and editor that works (almost) the same way in all of these platforms is a big win for me. Not to mention that I can code in any language I want with out switching editors.

Here is a short a short list features that made me change my mind.
* Cross platform support. (Big one).
* Lightweight. (When in the road, your battery will last longer).
* Fast as hell. You won't be waiting for minutes to open solutions.
* You can code in any language you want.
* Tiny footprint. You don't need 8 GB of disk's space just to install the tool.
* Already installed on most Unix systems.

Ok, that sounds good. But which features will you miss if you decide to give Vim a try?
Well, that heavily depends on your workflow, but based on fellow developers, I'll say:
* Built in Debugger.
* Smart refactors (a huge one for me too).
* Intellisense.
* Drag and Drop stuff around.
* There is no easy way to work with project and solutions files.
* Being able to use the mouse (really?!).

In general, I do TDD, so the builtin debugger it's not an issue to me. I always say that been in debug land is huge waste of time (almost as bad as being at meetings with project managers ;))
With regards to intellisense, you can use ctags to get some sort of intellisense (statement completion, quite frankly). It's not perfect, but it's good enough to get work done.
As far as refactors goes, I not gonna lie. Move code around without resharper is a bit of a pain in the ass; but as you will be working with a plain text editor, believe me, your code will be simpler and hence it won't be “that” hard to move around.

Note: I do know about omnisharp and I'm aware that it can provide almost the same Visual Studio's experience, but compared to plain old Vim, omnisharp is as slow as a dog. Not to mention you have to run a web server just to get intellisense. That sounds crazy to me.


Essential Vim plugins:
* CommandT. Resharper's Ctrl+N (kinda).
* MRU. Most recently used files.
* NERDTree. Directory/File explorer.
* Airline. Lightweight status line.
* Vim-CSharp. Better support for C# projects.
* SupertTab . Tab completion in insert mode.
* Snipmate. Vim's code snippets.
* Tcomment. Adds shortcuts to comment / uncomment code.
* Vim-Multiple Cursors. Simliar to Sublime Multiple Cursors.

External tools that will make your life easier:
* Exuberant Ctags.
* Git.

And last but not least, I haven't to be an all-in bet. Installing VsVim is a nice way to get a taste of Vim with out leaving your comfort zone. You wouldn't be able to use plugins, but I'll be good enough to get a taste of the powerful Vi motions and edit modes.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to create MS Word documents from Office templates using C#

By
The OpenXML SDK allows you to do pretty much anything you want with office files such as Excel, Word, etc… While many people like this library, I found it complex, unintuitive and poorly documented, not to mention the awful xml format that uses under the hood to represent the documents, styles, etc. So I decided not to use it and build my own solution. If you, like me, don’t like that library, you will find in this post an alternative approach to build word documents from templates using c#. A neat trick to work with Office is to use the macro recorder to understand how things work. The macro recorder allows you to start a macro, do something by hand, stop it, and then take a look at the generated VBA code. Once you do this, you are pretty much set. This is how it looks the template I’am going to use. Note: save the file as a Word template (.dotx) This is the code to create Word documents from C#: By running the code, you should get a document that looks...
23 comments
Read more

Printing html using the embedded web browser control

By
In this post I’ll try to answer some questions about the web browser control and provide some workarounds for known issues involved in the printing process. I'm assuming that you have some experience with the web browser control and basic knowledge of COM and hosting APIs. So I’m not going to cover those topics. At the bottom of this page I’ve added the links to download a small library I wrote that takes care of printing HTML and a demo app so you can try it out without having to write any code by yourself. Using the code The HtmlPrinter class will allow you to print html from an URL or just passing the html as string, you can also specify the title and the number of copies you want to print. The code may look something like this: Now that we know how to use the API let get answer some questions. Why my app crashes when I try to print multiple copies of a page? Well, apparently when you send a lot of print commands to the web browser control, ther...
21 comments
Read more

Migrating an ASP.NET MVC 4 app from Azure websites to WinHost

By
About a week ago I've to migrate an ASP.NET MVC 4/EF5 application from Azure websites to WinHost. While the process was really smooth, there were some caveats related to database connections that I want to share with you. Create and setup the ftp profile on VS and configure the connection string was really easy, WinHost provide you those values and there is nothing special here. But once you deploy your website and try to see it online, you may get the “yellow screen of dead” with the message: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)" Assuming you wrote the connection string properly, this happens because you cannot use the default connection name in your web.c...
2 comments
Read more