ASP.NET MVC Injecting Http/Request/Controller context

Question

Is there a recommended approach for injecting Http/Request/Controller context in an ASP.NET MVC application?

Previously I've only done this with HttpContext like so (I'm using StructureMap):

For<HttpContextBase>().Use(ctx => new HttpContextWrapper(HttpContext.Current));

However, in some cases I also need to get access to the request context. Rather than building this manually, it would be nice to have it injected. A good example would be injecting a UrlHelper (requires RequestContext and RouteCollection).

Thanks

Ben

Robin Clowers · Accepted Answer · 2011-03-28 17:11:08Z

4

You might want to consider whether you really want to depend on those context objects directly (they tend to make things that depend on them hard to test). That said, you are on the right track:

For<RequestContext>().Use(ctx => HttpContext.Current.Request.RequestContext);
For<RouteCollection>().Use(ctx => RouteTable.Routes);

answered Mar 28, 2011 at 17:11

Robin Clowers

2,16020 silver badges28 bronze badges

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

2 Comments

Ben Foster Over a year ago

Hi Robin, I generally only have these dependencies for purely contextual objects, for example a SiteContext context that abstracts access to things like current user etc. I can always mock HttpContextBase anyway. I did find this post too that looks interesting - kozmic.pl/2010/05/22/…

NimChimpsky Over a year ago

why does it make it harder to test, they are injected so can jsut be mocked in ? (I am about to do this, well I was about to do this)

Collectives™ on Stack Overflow

ASP.NET MVC Injecting Http/Request/Controller context

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related