[mattmanser]

When you first come across it it looks like they're console commands. Yay! You go, the light has been seen at MS! After mucking round with cmd and then power shell for a few minutes you realize, well, no, they're not. There's yet another window added to visual studio to run the commands and it installs a new directory and a crapton of pointless files in your project directory to boot. Woo. Like we needed more of them. And just to be extra useful it puts yet another option in the already vastly overcrowded and poorly organised right-click menu of projects.

I love visual studio and C#. But NuGet's pretty pants, it just feels like you're being treated like a child.

To me this just smacks of the overkill of the asp.net membership system to me. Vastly overcomplicated to do a simple job. Maybe I'm just getting cynical in my old age and it's time to switch to linux. There's lots of little things that bug me in .Net though so it's probably just one of my pet peeves. For example I've always detested the obsession asp.net has with ~ that for the most part is totally and utterly pointless.

With a lot of things MS seem to approach the problem with the most complicated use case in mind rather than the simplest.

[ern]

You mention the complexity of the ASP.NET membership system. I've always found it to be quite straightforward (unless you write your own providers I guess). Where are the pain points for you?

[teyc]

It was quite difficult for me when I first tried to pick up ASP.net. In retrospect, I don't think the problem is how difficult ASP.net provider system is, but the absence of assertiveness in the voice in tutorials. They tend to say, you an do it this using Forms Authentication, or Windows or Passport. Which is all true, but presents too many options to someone trying to find their way around a new system.

[skrebbel]

Thanks.

Sounds much like a matter of taste then, though. I much prefer clicking a button over typing a command (f.ex. tortoisegit over git, explorer over bash mv/cp/etc).