Difference between WebOperationContext.current and HttpContext.Current

Question

I develop web and mobile applications for my customers. In my current architecture, many resources are shared between the web access and mobile access. An aspx page can be shown on web and be called to a web view in a mobile app. My question is :

What is the difference between WebOperationContext.Current and HttpContext.Current object?

From my understanding it is the same object, but I noticed that WebOperationContext.Current is null in some cases and I don't understand why.

Roulette

Side note: WebOperationContext.Current Documentation and HttpContext.Current Documentation – Voltammeter

@Voltammeter : That was my first impulse, but I do not see the nuance between the two? – Roulette

I don't know if I should ask this as a separate question but I wanted to understand how these contexts are related to OperationContext. – Csch

Answer 1

WebOperationContext is typically used in a WCF REST method so that method can access the incoming request and outgoing response.

HttpContext is typically used in an ASP.NET WebForms page or web method for ASMX Web Service, when incoming request and outgoing response can be accessed.

They are designed for different project types (WCF REST/ASP.NET WebForms) so you should not use them in a wrong project type.

About when the value of .Current is null, that's even more complicated. Even if you are calling this property in the correct project type, you need to make sure the call is made on a proper thread. Only on the thread that handles the request (which also sends out the response) you can access the current context. On any other threads (background threads, or new threads created by you) you get null. This has been known for years but beginners still get it wrong sometimes.

Kisser

how to fix this . getting current object on new thread created by me. and sending response back to original thread, Should i use async await – Cinnamon