System.Web.Mvc Vs Microsoft.Web.Mvc

Question

I just started ASP.NET MVC, and the first thing that got me confused is on MSDN there is a System.Web.Mvc namespace, and then there is a Microsoft.Web.Mvc namespace. I'd like to know -

Why are there two different root namespaces for ASP.NET MVC framework library classes?
Based on what the classes go under one root namespace or the other?

Thanks in Advance.

NOTE: I did google search, and found nothing about it.

Why are the down votes and closing votes? I don't understand what is wrong in asking this question? Down voters, could you at least add a comment explaining your action? — atiyar
– atiyar, Commented Feb 11, 2016 at 1:55
Microsoft.Web.Mvc is the MVC Futures project. Refer Scott Gu's blog — user3559349
– user3559349, Commented Feb 11, 2016 at 2:20
@StephenMuecke: thanks for being helpful, and the link :) Could you please post this as an answer, so that I can accept? — atiyar
– atiyar, Commented Feb 11, 2016 at 3:09
@StephenMuecke: Please post your comment as an answer so that I can accept it. — atiyar
– atiyar, Commented Feb 11, 2016 at 3:23

user3559349 · Accepted Answer · 2016-02-11 03:38:08Z

5

The Microsoft.Web.Mvc namespace if for the MVC Futures project, which is for features that the MVC team may or may not include in future versions of ASP.NET MVC. There is very little documentation associated with it, but you can view the source code here.

As an example, it includes the Microsoft.Web.Mvc.Controls namespace, which is discussed in this blog, but it never got off the ground.

answered Feb 11, 2016 at 3:38

user3559349

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

System.Web.Mvc Vs Microsoft.Web.Mvc

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related