Skip to main content

Threads in .Net



Namespace: System.Threading

Thread class have Properties like IsAlive, IsBackground, IsThreadPoolThread, ManagedThreadId, Name, Priority, and ThreadState.

Thread class have Methods like Abort, Interrupt, Join, and Start.

Static Properties Include Thread.CurrentContext, Thread.CurrentPrincipal, Thread.CurrentThread.

Static Thread Methods include Thread.BeginCriticleRegion, Thread.EndCriticleRegion, Thread.GetDomain, Thread.GetDomainID, Thread.ResetAbort, Thread.Sleep, Thread.SpinWait, Thread.VolatileRead, and Thread.VolatileWrite

ThreadState enumerations are Aborted, AbortRequested, Background, Running, Stopped, StopRequested, Suspended, SuspendedRequested, Unstarted, and WaitSleepJoin.

Creating Thread:
                ThreadStart ts = new ThreadStart(mywork);
                Thread t = new Thread(ts);
                t.Start();

Use Thread.Join to make all thread complete their work before proceeding further.

ThreadPriority Enumeration is Highest, AboveNormal, Normal, BelowNormal, and Lowest.

To pass data to you method use Parameterized Thread start.

ParameterizedThreadStart ts = new ParameterizedThreadStart(mywork);
                Thread t = new Thread(ts);
                t.Start(“Hello”);

{Thread}.Abort can kill a thread at any time one may leave the data in inconsistent state. To handle this create Critical Regions around the code block that can leave data in inconsistent state.

Public static void mywork()
{
Thread.BeginCriticleRegion();
                ///Some Work
Thread.EndCriticleRegion();

                //Some more work
}

Execution Context Flow:
                Execution context automatically flows to the newly created threads. Context contains information about Security(IPrincipal), Localization(CultureInfo), Transaction information (System.Transaction). To stop this flow at the cost of the benefits provided by ContextInfo one can call ExecutionContext.SuppressFlow.

AsyncFlowControl afc = ExecutionContext.SuppressFlow();

ParameterizedThreadStart ts = new ParameterizedThreadStart(mywork);
                Thread t = new Thread(ts);
                t.Start(“Hello”);

ExecutionContext.RestoreFlow();
OR
flow.Undo()

ExecutionContext.Run can be used to run an arbitrary code along with custom Context Information. Like:

ExecutionContext ctx = ExecutionContext.Capture();
   //return copy of the current context
ExecutionContext.Run(ctx, new ContextCallback(mywork), null);
Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

Asynchronous Execution in ASP.NET

Asynchronous Execution: Two ways either implement IHTTPAsyncHandler interface or in ASP.NET 2.0 set <%@ Page Async=”true” %>. The second option implements IHTTPAsyncHandler interface automatically for the page when parsed or compiled. AddOnPreRenderCompleteAsync ( new BeginEventHandler(BeginTask), new EndEventHandler(EndTask)); AddOnPreRenderCompleteAsync() shoud be called in Page_load. The BeginEventHandler and EndEventHandler are delegates defined as follows: IAsyncResult BeginEventHandler( object sender, EventArgs e, AsyncCallback cb, object state) void EndEventHandler( IAsyncResult ar) AsyncProcess starts and completes between PreRender and PreRenderComplete. Other way to perform Async Task is using AsyncPageTask structure. It also allows multiple tasks to execute simultaneously. void Page_Load (object sender, EventArgs e) { PageAsyncTask task = new PageAsyncTask( new BeginEventHandler(BeginTask), new EndEventH...
Continue Reading »