Thread.BeginThreadAffinity Method ()
Notifies a host that managed code is about to execute instructions that depend on the identity of the current physical operating system thread.
Assembly: mscorlib (in mscorlib.dll)
Some hosts of the common language runtime, such as Microsoft SQL Server 2005, provide their own thread management. A host that provides its own thread management can move an executing task from one physical operating system thread to another at any time. Most tasks are not affected by this switching. However, some tasks have thread affinity - that is, they depend on the identity of a physical operating system thread. These tasks must inform the host when they execute code that should not be switched.
For example, if your application calls a system API to acquire an operating system lock that has thread affinity, such as a Win32 CRITICAL_SECTION, you must call EndThreadAffinity after releasing the lock.before acquiring the lock, and
Using this method in code that runs under SQL Server 2005 requires the code to be run at the highest host protection level.
The following example demonstrates the use of the EndThreadAffinity methods to notify a host that a block of code depends on the identity of a physical operating system thread.and
Imports System.Threading Imports System.Security.Permissions <SecurityPermission(SecurityAction.Demand, Flags:=SecurityPermissionFlag.ControlThread)> _ Friend Class MyUtility <SecurityPermission(SecurityAction.Demand, Flags:=SecurityPermissionFlag.ControlThread)> _ Public Sub PerformTask() ' Code that does not have thread affinity goes here. ' Thread.BeginThreadAffinity() ' ' Code that has thread affinity goes here. ' Thread.EndThreadAffinity() ' ' More code that does not have thread affinity. End Sub 'PerformTask End Class 'MyUtility
Requires full trust for the immediate caller. This member cannot be used by partially trusted or transparent code.
Available since 2.0