TargetedPatchingOptOut: “Performance critical to inline across NGen image boundaries”?

It tells NGen that it is OK to inline the method it’s applied to even in a different assembly.

For example:

  • String.Equals has [TargetedPatchingOptOut]
  • You write a program that calls String.Equals
  • You run NGen on this program for maximum performance
  • NGen will inline the String.Equals call, replacing the method call instruction with the actual code in the method.
    Method calls are (slightly) expensive, so this is a performance boost for frequently-called methods.

However, if Microsoft finds a security hole in String.Equals, they cannot just update mscorlib.dll, because that won’t affect the assembly that you just NGen’d. (Since it has raw machine code without referencing String.Equals).
I assume that if that were to actually happen, the security update would clear the NGen store.

Note that this attribute is only useful in the .NET Framework assemblies. You don’t need it in your own. You can find more information about that here: https://stackoverflow.com/a/14982340/631802

Leave a Comment