Probably these are two questions in one, I am using one EF context per request, but I want to use one per thread, because I am going to make some complex task in another thread during the request.
I need to perform periodically a certain task in my asp.net app so did like this:
I am trying to reproduce a threading error condition within an HTTP Handler.
We have an old 3rd party system (let’s call it Junksoft® 95) that we interface with via PowerShell (it exposes a COM object) and I’m in the process of wrapping it in a REST API (ASP.NET Framework 4.8 and WebAPI 2). I use the System.Management.Automation nuget package to create a PowerShell in which I instantiate Junksoft’s COM API as a dynamic object that I then use:
I am building a Blazor application with a REST API and Web interface. I will also have a monitoring part of the application that will poll data each second from a lot of different data sources. I have created a long running thread in a separate class that simply polls the data I want and it seems to be working fine. The application template I am using is a Blazor ASP.NET Server application. Simply like this:
I’m storing DataTable in ASP .NET Cache property. Operations that can be done on that DataTable are:
I have this simple code in aspnet :assuming no exceptions nor file locking nor process terminates :
I’m running a form in a second thread. If I do Ctrl-C to copy text on the clipboard, I get an Exception, “Current thread must be set to a single thread apartment (STA) before OLE calls can be made. (Using the clipboard involves OLE apparently).
Would changing a session variable (i.e. Session[“Progress”]) in code below be safe?
I have a process in a website (Asp.net 3.5 using Linq-to-Sql for data access) that needs to work as follows: