why does asp.net website project doesnot refer to x64 dll library?

Question

1.11/5 (2 votes)

See more:

I have a 64 bit dll reference in an asp.net website project. It doesnot build because I am referencing class from that dll. I have tried adding using namespace but still it does not run, it shows error at complietime.Please help me out.

Posted 14-Jan-16 1:20am

Member 11098660

Updated 14-Jan-16 1:25am

v2

Add a Solution

Comments

hypermellow 14-Jan-16 7:31am

What's the compile time error message?
What CPU are you targeting in your project build configuration? (x86/x64/Any CPU)
... are you building this on a x64 or x86 machine?

Member 11098660 14-Jan-16 8:06am

"type or namespace (x64dll name) doesnot exist..." . website project have only anyCpu in configuration manager. & I'm running vs2013 on win864bit.

hypermellow 14-Jan-16 8:51am

How did you add the reference?
In VS, when you right click the dll and select properties - what value does the Copy Local show?

Royston Malcomber 14-Jan-16 9:20am

In the configuration manager, select 'new' in the Active Solution platform drop down, select x64 and click OK.

Victor Tseng 12-Sep-18 23:19pm

Website project type doesn't support platform other than Any CPU. I also tried to manually modify the .sln file to add the x64 target but VS will just force change it back to Any CPU.

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2016-01-14T04:57:00

It's a bad idea to target your assemblies to any instruction-set architecture except "AnyCPU". But sometimes, you have to do that. This is only needed if one of the dependencies is a native (non-managed) module. On the local system supporting matching it can be considered acceptable.

But not for ASP.NET, unless you have a dedicated host and solve highly specialized problems. In nearly all cases, you should not assume any concrete instruction-set architecture. In case of mismatch, your solution won't work.

—SA