The attributes are combined using the bitwise OR operation as follows:
Code implementation masks:
Implementation information and interop masks:
Locking on the instance or on the type, as with the MethodImplAttributes.Synchronized flag, is not recommended for public types, because code other than your own can take locks on public types and instances. This might cause deadlocks or other synchronization problems.
Specifies that the method should be inlined wherever possible.
Specifies flags about code type.
Specifies that the method is not defined.
Specifies that the method implementation is in Microsoft intermediate language (MSIL).
Specifies an internal call.
Specifies that the method is implemented in managed code.
Specifies whether the method is implemented in managed or unmanaged code.
Specifies a range check value.
Specifies that the method implementation is native.
Specifies that the method cannot be inlined.
Specifies that the method is not optimized by the just-in-time (JIT) compiler or by native code generation (see Ngen.exe) when debugging possible code generation problems.
Specifies that the method implementation is in Optimized Intermediate Language (OPTIL).
Specifies that the method signature is exported exactly as declared.
Specifies that the method implementation is provided by the runtime.
Specifies that the method is single-threaded through the body. Static methods (Shared in Visual Basic) lock on the type, whereas instance methods lock on the instance. You can also use the C# lock statement or the Visual Basic SyncLock statement for this purpose.
Specifies that the method is implemented in unmanaged code.