I came into a shop that does a lot of .NET development over a year ago, and I swear I came into the experience hoping to learn what made lots of people say exactly what you've said.
6 months into it, I all but stopped caring, and overall, I felt like it actually created problems for me. But I'd like to understand what problems others feel it solved for them.
There's a difference between a platform (.net) and a programming language.
With visual studio, you develop for websites (MVC), apps (XAML based - WP, WPF, Silverlight, ...) and that makes it great.
I recently got back to android because of Android Builder and i'm still struggling with it (1 day or so). The visual studio experience is way smoother.
I have to admit, my little node.js experience with github and heroku felt awesome.. But it lacks a good IDE-experience and that is where Visual Studio really excels.
But command line tools can be integrated as wel in VS ;-), Azure is awesome to if you experimented with it.
With .Net you can integrate almost any language and Python is one of them.
I recently talked to someone who does his PHP work solely on Azure because of the platform.
I guess you have to get in the .Net platform fully (Linq / Entity Framework / DDD (Repository / Unity Of Work / ...) to really comprehend what i'm saying.
Honestly, coming into visual studio/c# from emacs/common lisp feels like going backwards in time for me.
Running my CL environment on Gentoo feels like the future; a not-quite-there-yet-but-still-awesome future; running VS on Windows feels like kiddie toys that haven't gotten around to growing up yet.
And that's a weird feeling when you realize the dollars, time, and research poured into each environment. :-)
The future! I can't imagine how anyone could say that. I started out with Smalltalk, then started doing C# professionally and eventually started doing CL in emacs. CL/SLIME/Emacs was by far the worst of that trilogy. I can't think of one single thing that the emacs combo did better or even as good.
Both Smalltalk and VS+Resharper have great refactoring tools. Both have great debugging tools (and in Smalltalk I can even do a lot of development right inside the debugger and watch how the code is reacting while I'm writing it). In the CL/Emacs setup debugging is so bad most people recommend not to even bother; just use tracing. And I can't understand why it needs to be like this, CL is closer to Smalltalk than it is C# (that is, CL is a "live" language as Smalltalk is or at least it very much can be. Even a compile-only CL like SBCL).
The other issue is project management. In Smalltalk it doesn't really come into play as much since the image is your "exe", but despite this Smalltalk has great tools for organizing classes, methods and so on (and Dolphin's way of letting your image be a "solution" and you make individual exes from that that drop everything they didn't use was absolutely brilliant). In VS, I create my assemblies, make dependencies and so on and the IDE just handles all this for me.
Contrast that with CL/Emacs: CL has ASDF files that can manage all your dependencies for you (people complain about it, but I've used them for several years and never had any problems) but you have to manage all this stuff manually. If you want a nice way of saying "create new package" or "create a new file that is in this package" you'll need to write all that handling, UI, etc. yourself. And after you write it all, what will you have? The interface will be hideous no matter how you do it because you're restricted to just text. In Visual Studio you can have the disapearable side bars approach, the "old school mac" approach of different info windows floating all over the desktop, etc. With emacs you'd be restricted to doing that stuff via ascii art or popping up more windows with ugly ascii art in them.
The only way I could see CL/Emacs as the future is if we're talking post-apocalyptic.
Well, as I stated: in Smalltalk I can trace statement by statement (compound statements work flawlessly), make a change to a method and the debugger does the right thing. With SBCL under SLIME on Emacs I have to fiddle around with optimize statements over and over, recompile mutliple times before debugging does anything at all, at which point it still doesn't work very well. Randomly skipping over sexpressions, etc., etc. The experience is awful and every time I've ask on #lisp I've been called an idiot for trying to debug instead of tracing (not even exaggerating, sadly).
That's funny because I feel the same way if I have to use Emacs. It feels like going back to the early 90s with some DOS Borland IDE.
Regular text editors just feel so clunky next to the cohesiveness of VS/Resharper or Intellij.
At some point in time, Emacs is going to have get overhauled to join the 90s, much less the 21st century.
And I understand that CL is a special case with Emacs, but it's still clunky as hell compared to what could have been really awesome environments (think Smalltalk environments), but with lots of resources pumped into the development.
You've kind of hit the key here, Visual Studio alone is decent, but Resharper is really what makes the experience for me. I don't know a single .net developer who could live without it.
I have hopes that LightTable will, when finished and released as open source, become the answer for those seeking a modern extensible editor. I love emacs, but there are times when I feel that it's my hair shirt.
Generally a terminal. Depending on the gnarliness of the path, maybe a file browser. I'm a very textual person. I'm sure that has something to do with it.
6 months into it, I all but stopped caring, and overall, I felt like it actually created problems for me. But I'd like to understand what problems others feel it solved for them.