badimageformatexception

I'm trying to embed SQLite into my portable C# .NET 2.0 application rather than having the DLL files included in the distribution folder. However, to embed SQLite, I cannot use the Mixed-Mode libraries provided by PHXSoftware. Instead, I am using their 'Managed Only' version. This works fine on 32-bit computers, but when it's running on a 64-bit machine, it throws a format exception. As I found out from here: http://sqlite.phxsoftware.com/forums/p/2564/9939.aspx I need to load the unmanaged sqlite3.dll manually in the required architecture format first before I use the managed libraries. That

Running CorFlags.exe against System.Data.SQLite.dll from http://sqlite.phxsoftware.com/ produces the following output. Version : v2.0.50727 CLR Header: 2.5 PE : PE32 CorFlags : 24 ILONLY : 0 32BIT : 0 Signed : 1 As you can see, 32BIT is not specified and PE is equal to PE32 . According to Moving from 32-bit to 64-bit application development on .NET Framework , this means that the assembly is Any CPU . However, using the assembly from a 64 bit application results in an error: System.BadImageFormatException: Could not load file or assembly 'System.Data.SQLite' or one of its dependencies. An

I am getting following runtime error, with my console application(VS2012) which refers to "dcasdk.dll". .Net Framework of the console app is 4.5, platform target is "Any CPU". Could not load file or assembly 'dcasdk, Version=1.0.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format. I used CorFlags application to check the target platform of the dll. Below are the details.. Version : v4.0.30319 CLR Header : 2.5 PE : PE32 CorFlags : 16 ILONLY : 0 32BIT : 0 Signed : 0 As per the information above, i think the dll is

Good day everyone. I have been having the same problem all day at work and am struggling to find any new paths to go down. I am getting the following error when my solution builds on server. I have no problem running/debugging all tests in the solution and it builds fine. Both server and my PC are x64. I have followed a lot of advice which I have found to no avail. I have set Platform Target to x86 for all projects in my solution under all configurations. I am aware that there is an nunit-console-x86.exe which could make all the difference but I'm not sure where to specify this in the code.

I have a project in c# that uses c++ library and some dlls. When I run it it works great. The library is Awesomium , contains both c++ library and c# wrappers When I create reference to this project from my ASP.NET MVC 4 project I get the following error: Exception Details: System.BadImageFormatException: Could not load file or assembly 'file:///D:\Projects\Development\ProGamers\GamingSite\bin\avcodec-52.dll' or one of its dependencies. The module was expected to contain an assembly manifest. Things I've tried: Coping the dlls, but it still doesn't work (The file exists). Registering it in the

I'm writing a plug-in for another program that is based on a public .NET API. Typically these plugins are made by creating a class library DLL that references the API assembly. Then a command class is created by inheriting from a base command class in the API assembly. The application is then set to reference the plug-in DLL file, and is then also responsible for actually firing up the custom command class when the user requests it. However, now I'm trying to automate some code generation through System.CodeDOM , and want to create a simple console application that automatically generates new

I have a DLL (FreeType) which is certainly 32-bit (header: IMAGE_FILE_MACHINE_I386). I want to use it from C# code, using DllImport. Target of my application is x86, IntPtr.Size is 4, process is 32-bit. But I get BadImageFormatException (Exception from HRESULT: 0x8007000B). What can be wrong? Of course I use 64-bit Windows 7. From what I understand, an assembly specifically built for x86 and running in a 64-bit operating system can only load libraries built for x86 or a BadImageFormatException will be thrown. In a 64-bit OS, an assembly built for Any CPU or x64 will throw the same exception