Building Project Problem with "Any CPU" Configuration

Question

1.00/5 (2 votes)

See more:

VS2010

Hi to all!!

I have a problem in building my executable project using "Any CPU" configuration. It says "The async result object is null or of an unexpected type". I need to build my applications in "Any CPU" configuration. At first it was ok then suddenly the problem came out and I dont know what's the reason behind this problem. When i run my application in "x86" configuration, its okay.

How can I solve this so that I can run my application in "Any CPU" configuration?

Can anyone help me on this. Thank you so much in advance.

God bless us all!!!

Posted 12-Feb-15 16:38pm

Romeland C. dela Peña

Updated 12-Feb-15 20:05pm

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 12-Feb-15 22:45pm

Are you saying that something works fine when the target architecture is different from "Any CPU"? Did you really try it? I would rather believe that the problem is unrelated to the target architecture. Anyway, you did not provide enough information to help you.
—SA

Rob Philpott 13-Feb-15 5:59am

If you find out what this is (perhaps one of the solutions below) please let us know. I am curious!

2 solutions

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)

Abhinav S · Answer 1 · 2015-02-12T20:14:00

Solution 1

The problem is related to the execution path being too long. If it is over 127 characters long, it can throw an error.
Try reducing the size of the assembly name.

Posted 12-Feb-15 20:14pm

Abhinav S

OriginalGriff · Answer 2 · 2015-02-12T20:17:00

Solution 2

Check your project references: chances are that you are using an assembly which is built for x86 only.
Also check any DllImport libraries to make sure they are available in 32 and 64 bit versions. If you build an "any CPU" app with a 32 bit external code you will get such problems.

Posted 12-Feb-15 20:17pm

OriginalGriff