The cross-thread usage of “HttpContext.Current” property and related things
I read from < Essential ASP.NET with Examples in C# > the following statement:
I read from < Essential ASP.NET with Examples in C# > the following statement:
I’m in the process of updating a library that has an API surface that was built in .NET 3.5. As a result, all methods are synchronous. I can’t change the API (i.e., convert return values to Task) because that would require that all callers change. So I’m left with how to best call async methods in a synchronous way. This is in the context of ASP.NET 4, ASP.NET Core, and .NET/.NET Core console applications.
I’ve been told that ASP.NET is multithreaded by default in IIS. How is this threading achieved?
Why is this happening when we make a call to the AccountApiController.Register() method?
I have a component that needs to store static values fore each thread. It’s a general component that can be used in many scenarios and not only in ASP.NET.
I need to execute an infinite while loop and want to initiate the execution in global.asax.
My question is how exactly should I do it? Should I start a new Thread or should I use Async and Task or anything else? Inside the while loop I need to do await TaskEx.Delay(5000);
I got a thread that is just banishing.. i’d like to know who is killing my thread and why.
i’m creating asmx web service and have to create thread to do background IO to refresh system data. What is the right way? I’m not interested to get any results to creating thread. I just want the ASP.NET worker thread to create a thread that does it’s loading and in the end makes one assign (I think assign _alldata = newData is atomic where both instances of my own big structure class SystemData) so the worker thread that created the the new thread can propagate instantly.
I am using the code below to download multiple attachments from a TFS server:
The user does something on the ASP.Net page that causes my server-side code to need to connect to another system and carry out lengthy operations, so I want to return control to the user quickly by firing that action to another thread. The user can keep watching progress through AJAX or simply move away – the web is stateless after all 🙂