Having used multiple languages and technologies, I'm not even slightly impressed by VS.

I've use VisualStudio every day for the past years. And honestly there are a lot ideas they could borrow from other tools like Eclipse.

Some examples that I personally feel are ways that C# in VS is lackluster compared to Java in Eclipse.

No proper automatic build. While the stuff in Eclipse is a bit too aggressive sometimes it's really one of those really cool features to have.

Errors, warnings, other tools like StyleCop don't show errors inline with the code. I mean, really? I have to scroll through the error list and click?

It also doesn't really seem to understand the code it's processing. I'd expect that when I'm working on Silverlight with C# that the premiere tool from Microsoft should be able to handle things like refactoring properties in C# where it would update automatically in XAML.

And this is not even mentioning the complete trainwreck that is MSDN. Perhaps you can understand it once you really get into it, but I find it extremely confusing the way it mixes different frameworks with similar but subtly different functionality. (Eg a lot of things in Windows Phone are similar, but not identical, to features in .Net and trying to find the "chain of classes" that are relevant to your code is not nearly easy enough.)

Some of these things are probably things you can fix with extensions like Reshaper. But in the end you'll pay hundreds of dollars to compete with something that is free in Eclipse.

MVC4 would be blocked by:

> MVC4 - Partial, no async features supported. > ASP.NET 4.5 Async Pipeline - Needs an parallel processing pipeline with async support, not done.

Still doesn't change the fact that these techs are one of the best ever made.