Asp.Net MVC Shared Controllers

Question

I Have small question about general convention:

Is Creating some controllers that we can call "shared" in general is a good approach? What do You think about that, and maybe You have some alternatives ?

i.e. : I have controller "User" - It's common controller, some authenticate method, profile edit etc. Beside that I create "UserShared" controller - I'll use it in many views (Html.RenderAction) to get some PartialViews i.e. AccountMenu, MessageStatus etc. My intention of that approach is to make views as dumb as it's possible and don't mix "shared" (in most cases returns only PartialViewResult) actions and common one.

Tassadaque · Accepted Answer · 2011-10-31 21:06:02Z

2

If functionality is common across controller you can use base controller. Some may argue against it due to coupling issue. You may read here and here

answered Oct 31, 2011 at 21:06

Tassadaque

8,19715 gold badges59 silver badges92 bronze badges

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

3 Comments

mgibas Over a year ago

Ok, I understand what You mean, but I thought about actions shared between many Views, not Controllers- about actions i.e. that returns PartialViews with some menu. And then I Can use it in an View like that: @Html.RenderAction("GetUserRelatedMenu","UserShared")

Tassadaque Over a year ago

I have implemented the menue using shared controller and it works fine. Have u any reference regarding your idea

mgibas Over a year ago

No - that's why I'm asking :)

Collectives™ on Stack Overflow

Asp.Net MVC Shared Controllers

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related