title: MVC, not "supposed" to use HttpContext.Current anymore?
body: <p>Someone in a post <a href="https://stackoverflow.com/questions/2497575/asp-net-mvc-unit-test-controller-with-httpcontext">here</a>, commented that you should not use HttpContext.Current when using MVC, rather, you should be using <a href="http://msdn.microsoft.com/en-us/library/system.web.mvc.controllerbase.controllercontext.aspx" rel="nofollow noreferrer">ControllerBase.ControllerContext</a>.  In some respects, this makes sense, but in other respects it doesn't.  </p>
  
  <p>For example, ControllerContext is an instance variable, so everywhere I want to reference, say, my Session variables, I need to have a reference to the Controller?  Why are we "not supposed" to be using HttpContext.Current in MVC, when you still can?  Is there an "appropriate" MVC "way" to get at my Session object without having to have a reference to the Controller?  </p>
  
  <p>I know test-wise, it is better for reasons stated in many other places, but I am working on a project that manages Session variables and references HttpContext.Current and I want to know if there is a better way to get my hands on the Session object without passing a reference to the controller.</p>