Update documentation on MethodBase.Invoke invokeAttrs parameter

[serhiiz]

It seems the documentation on System.Reflection.MethodBase.Invoke in regard to the invokeAttr parameter is outdated.
According to the documentation:

invokeAttr BindingFlags
A bitmask that is a combination of 0 or more bit flags from BindingFlags. If binder is null, this parameter is assigned the value Default; thus, whatever you pass in is ignored.

the invokeAttrs parameter is ignored when the binder parameter is null. However, that doesn't seem to be accurate. According to the implementations (System.Reflection.RuntimeMethodInfo.cs, System.Reflection.Emit.DynamicMethod.CoreCLR.cs, System.Reflection.Emit.DynamicMethod.CoreCLR.cs), the invokeAttrs is never ignored. Unless I'm missing something.

Summary

The suggestion is to take out the statement about invokeAttr being ignored when the binder is null.

[learn-build-service-prod]

Learn Build status updates of commit 5cd4e9d:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.Reflection/MethodBase.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[steveharter]

LGTM; the only flag that would be used without a binder is BindingFlags.DoNotWrapExceptions but I don't think calling that out is necessary.