-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MethodInfo.Invoke #579
Comments
I could repro this. It happens when you click on the TOC link that takes you to https://docs.microsoft.com/en-us/dotnet/api/system.reflection.methodinfo.invoke?view=netframework-1.1 |
@dend Is this your area? |
@mairaw is the method available in the newer versions of .NET Framework? |
It's inherited from the parent class in newer versions @dend |
I don't see its DocID in the FrameworksIndex file for 4.7.2. @mairaw - can we look at the assembly where it is, to make sure we are not missing anything in |
This is duplicate of #347 and is tracked with the bug above, so closing this item 😄 |
Do you also have a duplicate label @dend? Easier to see when scanning issues. |
I'm wondering if this issue should be reopened, @dend. It doesn't seem like it's a strict duplicate of #374. The problem here is twofold:
The reason is that, in .NET Framework 1.1 through 3.5, MethodInfo provided an implementation of these methods. However, the implementations were identical to the base class MethodBase implementations, so in .NET Framework 4, the MethodInfo implementation was removed. |
Can we reopen this @Powerhelmsman @dend based on @rpetrusha's feedback? |
Assigning to @mimisasouvanh as the PM driving the .NET experience. |
I don't see Invoke listed under later versions anymore, so closing this. |
Original issue https://github.com/dotnet/docs/issues/6822 from @NetMage
MethodInfo.Invoke link under Methods in Tree goes to .Net 1.1 page instead of MethodBase.Invoke page.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: