Saturday, July 26, 2008

ASP.NET MVC - Branding?

I am not sure ASP.NET MVC is really the best name for the MVC architecture that the ASP.NET team is creating. Said name stresses the fact that it is still ASP.NET. Most people I know think of ASP.NET WebForms (and more specifically, postbacks and the event model) when they think of ASP.NET. Perhaps if they started a marketing campaign to rebrand:


Old NameNew Name
ASP.NET WebFormsWebForms
ASP.NET MVCWebViews
Web development in .NET overallASP.NET

This might be better as I think it would get rid of the misconception that ASP.NET means events and runat="server" all over the place. Books and such could brand themselves with "ASP.NET" and have sections split off for WebForms and WebViews (or they could brand with just WebForms or just WebViews and ASP.NET wouldn't be necessary in the title). Think: WebViews in C# 4, WebForms for WinForms developers in 2010 and ASP.NET 4.0 Bible vs. ASP.NET MVC 2.0, ASP.NET for WinForms developers in 2010 and ASP.NET 4.0 Bible. Which set makes it easier to understand what you are looking for while at Amazon?

Edit: if anyone at MS is reading this (or anyone writing a book with the titles mentioned), I claim no rights whatsoever to "WebViews" as a name or anything like that (other than to say that this post stays as pure speculation and I don't have to take it down for any reason). This was just an idea that popped into my head this morning.

1 comment:

Anonymous said...

I think that is an excellent suggestion. Probably the best I've heard for naming this mess.