VC# 2008 interop code not working on VC# 2010

Question

0.00/5 (No votes)

See more:

VS2008

VS2010

, +

Hi I am using VS 2010 Express and have ported some code proven in VS 2008 but it fails in VS 2010 and I cannot understand why.
The code uses InvokeMember:

<object>.Interface.GetType().InvokeMember("<Method Name>",
                                System.Reflection.BindingFlags.InvokeMethod,
                                null, <Object>.Interface, new object[] { <params> });

It works fine in VS 2008 but not in VS 2010, exception thrown is "Value does not fall within the expected range." The code and references are identical, the <object> is not null.
Baffled.
Any ideas?

Posted 2-Feb-11 7:40am

aaawesome

Updated 2-Feb-11 7:42am

Yusuf

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Henry Minute · Answer 1 · 2011-02-02T07:50:00

Solution 1

Might the causes in this thread[^] be related to your problem?

Posted 2-Feb-11 7:50am

Henry Minute

Comments

aaawesome 3-Feb-11 4:27am

Thanks for the reply, but no luck. The code I am using is identical so the issue should have arisen in VS2008 if it was the issue described in the article but this worked fine in VS2008.