Hello,

I was just curious if anybody knew the reason sometimes you refer to the corrent context as HttpContext.Current, and sometimes it is Context.Current. As an example, I'm building a class outside of the web application, and it worked using Context but not HttpContext.

Is HttpContext specified in the web domain only, and context is used elsewhere?

Just curious.

Brian

__________________
Brian

Brian,

Chances are what you are seeing is just a side effect of the code scope.

When you are in a web application, you'll typically be coding on a page (System.Web.UI.Page). "Context" is a member of "System.Web.UI.Page". Outside of the scope of a page class, you can only see it be means of the static reference via "System.Web.HttpContext.Current".

Not sure if you have them backwards in your post or not, but this is what I have found to be the case.

I have a web control library, that has a class that inherits from System.Web.UI.Control; I managed to get it to work with Context.Current.

I figured that was it, but wasn't sure....

Brian