Comments on: Coding: Role based interfaces

By: Dave Cameron

Dave Cameron — Thu, 22 Oct 2009 04:03:03 +0000

@Mark: I quite like this, and your explanation. It seems a very good example of tell-don’t-ask, or at least east-oriented code. Introducing the interface should make it easier to break in to a separate class, if we really need to.

@Daniel: We already use an IoC container in this code base. Unity. At the time the controller is resolved, we don’t know which content we need. And, with the exception of one item, we don’t resolve anything afterwards. We could, but this solution seems tidy for the time being.

By: DotNetShoutout

DotNetShoutout — Mon, 19 Oct 2009 15:23:07 +0000

Coding: Role based interfaces – Mark Needham…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

By: Daniel Marbach

Daniel Marbach — Mon, 19 Oct 2009 07:33:27 +0000

Hello Mark,
Why not using an IoC framwork? For example ninject allows you to do context sensitive binding that allows you to specify what kind of concrete instances need to be injected when a type is requested in a specific context. That would solve all your problems

Daniel

By: Reflective Perspective - Chris Alcock » The Morning Brew #457

Reflective Perspective - Chris Alcock » The Morning Brew #457 — Mon, 19 Oct 2009 07:32:49 +0000

[...] Coding: Role based interfaces – Mark Needham discusses how you can support different user interfaces for users in different roles using the MVC pattern [...]