[release/8.0] Add late binding lookup in VB.NET for COM objects

[github-actions]

Backport of #91399 to release/8.0

/cc @AaronRobinsonMSFT

Customer Impact

Late bound look-up on COM objects fails in Visual Basic, but works using C#'s dynamic keyword - see #90541.

Testing

Validated with customer repro application. Sharing private build for further validation.

Risk

Low. This only impacts Visual Basic scenarios involving late-bound COM objects.

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

[ghost]

Tagging subscribers to this area: @cston
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #91399 to release/8.0

/cc @AaronRobinsonMSFT

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author:	github-actions[bot]
Assignees:	-
Labels:	area-Microsoft.VisualBasic
Milestone:	-

[jeffschwMSFT]

approved. once ready you can merge.

[carlossanlop]

@AaronRobinsonMSFT would you mind filling out the template in the PR description? Just to make sure it's well documented.

[carlossanlop]

Btw this is still marked as no merge. Ping me when it's ready.

[AaronRobinsonMSFT]

Btw this is still marked as no merge. Ping me when it's ready.

Yep. We are waiting on customer validation before merge.

[AaronRobinsonMSFT]

@carlossanlop We have confirmation from the customer this fix addresses their issue. I've just merged tip into this branch. Should be ready to go once green. I will ping you once I see it.