deploy c# 32bit application log4.net

Question

0.00/5 (No votes)

See more:

Hello guys,

I've app that I want to deploy it on 32bit. When I change to 32 bit, it gave me this error:

File 'log4net.dll' targeting 'AMD64' is not compatible with the project's target platform 'x86'

Posted 31-Mar-13 7:22am

Member 8584763

Add a Solution

Comments

Sergey Alexandrovich Kryukov 31-Mar-13 21:27pm

I don't know where you got "AMD64". .NET usually use the term "x86-64" for this instruction-set architecture, in contrast to "Itanium" (another 64-bit this instruction-set architecture). You cannot mix them in one process; it never ever works.
—SA

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 · 2013-03-31T15:33:00

Solution 1

Please see my comment to the question. Compile all the assemblies used in your process to the same target instruction-set architecture (http://en.wikipedia.org/wiki/Instruction_set[^]).

Prefer using the target "AnyCPU", them the actual target will be determined by the platform when the application is loaded. If one of the components (.NET assemblies or unmanaged code modules) still have to be compiled for some particular architecture, the final architecture is defined by targeting the entry assembly of the application.

With Visual Studio, please see the project properties window.

—SA

Posted 31-Mar-13 15:33pm

Sergey Alexandrovich Kryukov

Comments

Member 8584763 1-Apr-13 7:47am

I used in my project x86 and for deployment I used the same x86.

when I used x64 and for deployment I used the same x64. It didn't give me any error, but I need it to work on x86?

That's when I get the error.

Sergey Alexandrovich Kryukov 1-Apr-13 9:15am

Is you need to work on x86, you need to build your entry assembly of the application to the target x86, and all other assemblies can be "AnyCPU" or x86, but nothing else. The thing is: OS will support two targets: one is its native x86-64 (or Itanium), the second one is compatibility x86 which can be executed on WoW64. You need to tell OS about it, that's why you need to have the entry assembly built to a certain target (not "AnyCPU").

But why not having deployment for x86-64? Of course, if some of your customers uses x86, you would need to support it. Usually, it is done via "AnyCPU", unless you have some CPU-specific (unmanaged) modules.

I would also advise to build everything from source; don't use pre-built DLL or something...

—SA

Member 8584763 1-Apr-13 9:51am

I tried to put "Any CPU" and for the deployment I put x64 it works, but when I put x86, it didn't work?

Do you think the problem is CR?

Sergey Alexandrovich Kryukov 1-Apr-13 10:36am

You need to take into account each and every of the factors I mentioned before.
You should know targets of all assemblies of your project and the platform's. You you cannot analyze it by your self, list them all.
—SA

Member 8584763 1-Apr-13 11:47am

There're as followings:

stdole.dll
log4net.dll
Microsoft.VisualC.STLCR.dll
CrystalDecisions.Data.AdoDontNetInterop.dll
CrystalDecision.Shared.dll
CrystalDecision.ReportSource.dll
CrystalDecision.ReportAppServer.Prompting.dll CrystalDecision.Enterprise.Viewing.ReportScource.dll

Sergey Alexandrovich Kryukov 1-Apr-13 11:51am

OK, now, to what target are they compiled, each of them?
—SA

Member 8584763 1-Apr-13 11:56am

I didn't understand your question?

Sergey Alexandrovich Kryukov 1-Apr-13 12:02pm

"AnyCPU", "x86".., each of them... This is the key.
—SA

Member 8584763 1-Apr-13 12:03pm

x86

Sergey Alexandrovich Kryukov 1-Apr-13 13:18pm

OK, if they all were x86, you would not have this problem. Did you specify "x86" for your entry assembly as well?
You are reporting an error which says that at least one is x86-64. Which one? Do you have source code?
—SA

Member 8584763 1-Apr-13 13:30pm

Well, I don't think all the assembly are x86 some of them are x64.

Because this problem don't occur when I deploy it for x64?
How can specify the assembly?

Sergey Alexandrovich Kryukov 1-Apr-13 13:38pm

There is no such thing as "x64"!
Apply simple logic, starting from basic facts I tries to explain. None of the possible mixtures of target CPU architectures can work. If something worked as x86-64, it means all the assemblies are x86-64 (and proper GAC assemblies are referenced), which means that some are x86-64, some are "AnyCPU". If you want x86 (on what platform?), you need to eliminate any of x86-64 or Itanium.
Either eliminate them, of admit that you only have x86-64 code.
—SA

Member 8584763 1-Apr-13 13:46pm

I'm confused, I thought x86 for Windows 32 cpu and x64 for Windows 64 cpu

Who can I distinguish between those assembly?

Sergey Alexandrovich Kryukov 1-Apr-13 13:57pm

Not only. Plus WoW64, which makes the problem:

http://en.wikipedia.org/wiki/WoW64

When the entry assembly claims AnyCPU, OS tries to use its native CPU architecture, and only if you explicitly build with "x86", it tries to use WoW64 and load the process as x86. And then, if any x86-64 or Itanimum (IE-64) sneaks in, it "works" but may crash, or something...

I mentioned it before, but you probably did not pay attention.
—SA

Member 8584763 1-Apr-13 14:01pm

The assembly are added automatic.

Can you send me your email to check it?

Sergey Alexandrovich Kryukov 1-Apr-13 14:07pm

No, sorry.

You are right about "added automatically". You should not worry about GAC assemblies, I tried to explain that already...
Let me ask this: in your solution, do you have a single assembly referenced as the name of the executable module, such as *.DLL?
If you only used GAC + some projects in full source code referenced as "Project" (not via "Browse"), you would not have any problems.
—SA

Member 8584763 1-Apr-13 14:50pm

Ye I have
What about your email can I send my project to you

Sergey Alexandrovich Kryukov 1-Apr-13 15:02pm

Not before you answer all my questions...
And — is it source code only, or do you have any binaries in the project? A need to install anything?
—SA

Member 8584763 1-Apr-13 15:27pm

Yes it is code with install crystal report

Sergey Alexandrovich Kryukov 1-Apr-13 15:41pm

I'm not going to install anything, sorry. I explained basic principles to you, you should draw the conclusions...
—SA