Rails, Django, Monorail, Struts, SproutCore, Symfony... these are all fairly snappy names for web MVC frameworks.

But we have "ASP.NET MVC"?? Seems verbose and inelegant to me. I've tried telling my friends about the ASP.NET MVC framework who don't work in the Microsoft space and several times, when they've asked me what it's called, I have to say "it's just called the ASP.NET MVC framework."

Is anyone else annoyed by this? Are there are any plans to brand it properly when it comes out of preview/beta mode?

What's wrong with calling a duck a duck?  I guess I am the exact opposite.  I get tired of looking up terms like Rails, Struts, etc because I don't have a clue what they are from the name.

If they give it some snappy marketing name, you will see lot's of conversations like this:

"Hey I have been using {insert snappy marketing name here} recently and it is really good!"

"What the heck is {insert snappy marketing name here}?"

"It is the MVC Framework for ASP.NET!"

If you just say "Hey I have been using ASP.NET MVC" it cuts out a meaningless step in that conversation.

dmorrison:

Are there are any plans to brand it properly when it comes out of preview/beta mode?

Looking at Microsoft's history of branding products, it is branded properly, for better or worse. :)

 ASP.NET MVC is a  meaningful name.

Please, please, please... don't rename ASP.NET MVC

Remember Atlas? It was nice name, and at the end it became only MS AJAX.

I like the current name ASP.NET MVC, which is so cool. 

ASP.NET MVC

ASP.NET WebForm

ASP.NET Ajax

They're like a family.

panjkov:

Remember Atlas? It was nice name, and at the end it became only MS AJAX.

Frankly I think the name Microsoft AJAX Library is more meaningful than Atlas (thought it was indeed a nice codename with a cool msn like logo of a guy holding a globe in his neck).

Grz, Kris.