UNC Path and Unhandled Exception: System.BadImageFormatException in C#

Question

I compiled the whole project with x86 platform target. It is working fine when I copy .exe and the reference dlls on to the server and run .exe from server cmd window.

Our requirement is to copy the exe and dlls onto some network path and execute the exe on the server using UNC path. When I execute using UNC path, I am getting the error:

Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'XXXX, Version=3.0.10.19399, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format. File name: 'XXXX, Version=3.0.10.19399, Culture=neutral, PublicKeyToken=null'

WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Can someone help?

What happens when you enable Assembly Bind logging as the message suggests? — Dai
– Dai, Commented Jun 21, 2012 at 16:19

Onkelborg · Accepted Answer · 2012-06-21 16:28:14Z

0

I'm just guessing now, but I would probably blame the path itself - it's most likely "untrusted", reason unknown. Enable Assembly Bind Logging (tip: google :) ) to figure out what's happening

answered Jun 21, 2012 at 16:28

Onkelborg

4,0251 gold badge23 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

UNC Path and Unhandled Exception: System.BadImageFormatException in C#

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related