Can't access to HttpContext.Current [duplicate

问题:

This question already has an answer here:

• HttpContext.Current not Resolving in MVC 4 Project 3 answers

I can't access to HttpContext.Current on my project MVC4 with C#4.5

I've added my reference to System.Web in my project and added the using instruction on my controller page...

But I can access currentHandler only...

var context = HttpContext.CurrentHandler; //Current

Is HttpContext.Current deprecated on C#4.5 ?

I've looked this help page : http://msdn.microsoft.com/en-us/library/system.web.httpcontext.aspx

回答1:

Have you included the System.Web assembly in the application?

using System.Web;

If not, try specifying the System.Web namespace, for example:

 System.Web.HttpContext.Current

回答2:

This is because you are referring to property of controller named HttpContext. To access the current context use full class name:

System.Web.HttpContext.Current

However this is highly not recommended to access context like this in ASP.NET MVC, so yes, you can think of System.Web.HttpContext.Current as being deprecated inside ASP.NET MVC. The correct way to access current context is

this.ControllerContext.HttpContext

or if you are inside a Controller, just use member

this.HttpContext

回答3:

Adding a bit to mitigate the confusion here. Even though Darren Davies' (accepted) answer is more straight forward, I think Andrei's answer is a better approach for MVC applications.

The answer from Andrei means that you can use HttpContext just as you would use System.Web.HttpContext.Current. For example, if you want to do this:

System.Web.HttpContext.Current.User.Identity.Name

you should instead do this:

HttpContext.User.Identity.Name

Both achieve the same result, but (again) in terms of MVC, the latter is more recommended.

Another good and also straight forward information regarding this matter can be found here: Difference between HttpContext.Current and Controller.Context in MVC ASP.NET.