Click to Rate and Give Feedback
MSDN
MSDN Library
.NET Development
.NET Framework 3.5
 MethodImplOptions Enumeration

  Switch on low bandwidth view
This page is specific to
Microsoft Visual Studio 2008/.NET Framework 3.5

Other versions are also available for the following:
.NET Framework Class Library
MethodImplOptions Enumeration

Defines the details of how a method is implemented.

This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values.

Namespace:  System.Runtime.CompilerServices
Assembly:  mscorlib (in mscorlib.dll)
Visual Basic (Declaration)
<SerializableAttribute> _
<ComVisibleAttribute(True)> _
<FlagsAttribute> _
Public Enumeration MethodImplOptions
Visual Basic (Usage)
Dim instance As MethodImplOptions
C#
[SerializableAttribute]
[ComVisibleAttribute(true)]
[FlagsAttribute]
public enum MethodImplOptions
Visual C++
[SerializableAttribute]
[ComVisibleAttribute(true)]
[FlagsAttribute]
public enum class MethodImplOptions
JScript
public enum MethodImplOptions
Member nameDescription
Supported by the .NET Compact FrameworkSupported by the XNA FrameworkUnmanaged Specifies that the method is implemented in unmanaged code.
Supported by the .NET Compact FrameworkSupported by the XNA FrameworkForwardRef Specifies that the method is declared, but its implementation is provided elsewhere.
Supported by the .NET Compact FrameworkSupported by the XNA FrameworkPreserveSig Specifies that the method signature is exported exactly as declared.
Supported by the .NET Compact FrameworkSupported by the XNA FrameworkInternalCall Specifies an internal call. An internal call is a call to a method that is implemented within the common language runtime itself.
Supported by the .NET Compact FrameworkSupported by the XNA FrameworkSynchronized Specifies that the method can be executed by only one thread at a time. Static methods lock on the type, whereas instance methods lock on the instance. Only one thread can execute in any of the instance functions, and only one thread can execute in any of a class's static functions.
Supported by the .NET Compact FrameworkSupported by the XNA FrameworkNoInlining Specifies that the method cannot be inlined.
NoOptimization 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.

This enumeration is used with the MethodImplAttribute enumeration.

You can specify multiple MethodImplOptions values by using the bitwise OR operator.

NoteNote:

Locking on the instance or on the type, as with the 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.

Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98, Windows CE, Windows Mobile for Smartphone, Windows Mobile for Pocket PC, Xbox 360, Zune

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

.NET Framework

Supported in: 3.5, 3.0, 2.0, 1.1, 1.0

.NET Compact Framework

Supported in: 3.5, 2.0, 1.0

XNA Framework

Supported in: 3.0, 2.0, 1.0
Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Behavior of NoInlining      jader3rd ... Noelle Mallory - MSFT   |   Edit   |   Show History

Does the NoInlining field mean that this method can't be inlined into other methods, or does it mean that no inlining will occur within this method?

[Noelle Mallory - MSFT] Please post questions to the MSDN Forums at http://forums.microsoft.com/msdn. You will likely get a quicker response through the forum than through the Community Content.

Tags What's this?: Add a tag
Flag as ContentBug
MethodImpOptions.NoOptimization was introduced in .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1      David M. Kean   |   Edit   |   Show History
The MethodImpOptions.NoOptimization value was introduced in .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1.
Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker