Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
BadImage Format Exception
| Article ID | : | 949625 |
| Last Review | : | February 23, 2008 |
| Revision | : | 1.2 |
Source: Microsoft Support
Back to the top
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Back to the top
Action
A .NET 2.0 C# application refers to a 32-bit unmanaged dll. The application is built using C# on Visual Studio 2005 with the “AnyCpu” platform setting.
Back to the top
Result
The application runs fine on 32-bit machine but when it is launched on a 64-bit machine, it throws a BadImageFormatException.
"Unknown exception error hresult:0x8007000B,” which maps to BadImageFormatException.
Back to the top
Cause
In this case, the managed C# application is not a pure managed application because it refers to a 32-bit unmanaged or native dll.
The 'AnyCpu' switch has the following results:
- A 32-bit process on a 32 bit machine
- A 64-bit process on a 64 bit machine
A 32-bit dll cannot be loaded in a 64-bit process or vice-versa. Hence, when an application running in a 64-bit process tries to load a 32 bit dll, it fails with BadImageFormatException. Simillarly, when an application running in a 32-bit process tries to load a 64-bit dll, it fails with a BadImageFormatException.
Back to the top
Resolution
When a managed application refers to a native cpu or platform specific dll, it should not be build using the ‘AnyCpu’ switch.
Back to the top
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Back to the top
APPLIES TO
| • | Microsoft .NET Framework 1.0 |
| • | Microsoft .NET Framework 1.0 Service Pack 3 |
| • | Microsoft .NET Framework 1.1 |
| • | Microsoft .NET Framework 1.1 Service Pack 1 |
| • | Microsoft .NET Framework 2.0 |
| • | Microsoft .NET Framework 2.0 IA64 Edition |
| • | Microsoft .NET Framework 2.0 Software Development Kit |
| • | Microsoft .NET Framework 2.0 x64 Edition |
| • | Microsoft .NET Framework 3.0 |
| • | Microsoft .NET Framework 3.5 |
Back to the top
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please