32bit-64bit

Yet another “could not load file or assembly … or one of its dependencies. The system cannot find the file specified”

蓝咒 提交于 2019-12-01 17:29:21
I have a dll with NUnit tests that had been working fine. I converted it from an Any CPU to an x86 project because I need to use SQLite reliably across different platforms, so I need to include the 32-bit System.Data.SQLite.dll and let everything reference that. Anyway, after conversion, NUnit gives that error when trying to load the dll. I don't think this will be enlightening at all, but here is the stack trace: System.IO.FileNotFoundException: Could not load file or assembly ... or one of its dependencies. The system cannot find the file specified" Server stack trace: at System.Reflection

Using a 32 bit dll on a 64 bit machine

China☆狼群 提交于 2019-12-01 17:15:00
I have an old project which uses a 32 bit dll. This works fine on 32 bit processor, however when I install the same project on a 64 bit OS it does not work. Is there any way to convert 32 bit dll to 64 bit? Is there an alternative solution solution to make my 32 bit dll work in a 64 bit OS? Your 32 bit dll should work just fine on a 64 bit machine as long as it is loaded into a 32 bit process - attempting to load a 32 bit dll into a 64 bit process will fail. If your project is a .Net (e.g. C#) application then you should be able to target your assembly at x86 in order to get your 32 bit dll

nUnit Exception on a 64 bit Machine

不羁岁月 提交于 2019-12-01 16:42:07
I have an MVC 3.0 app. My testing framework is nUnit 2.4.8.0. I started this code on a 32 bit machine, and recently started using a 64 bit machine. I just as recently upgraded the project to .NET 4.0. My application runs fine - I am able to hydrate my objects from the database appropriately. The issue is when I run my integration tests. The tests fail, and give an exception I've never seen before: NHibernate.ADOException : cannot open connection ----> System.BadImageFormatException : An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) I've

Error building 32-bit OS X app?

倖福魔咒の 提交于 2019-12-01 16:09:13
I'm working on my first Mac OS X app. My project was set-up with XCode defaults and I haven't touched any Build Settings. When building for Mac 64-bit, the app runs fine. However, when building for Mac 32-bit, I get a seemingly arbitrary error that says: Semantic issue: Synthesized property 'myProperty' must either be named the same as a compatible ivar or must explicitly name an ivar. What kind of things can I check for? It sounds like you have found the error but I think I can answer your question just in case someone else later finds it. Apple has made a lot of changes in the 64 bit

printdialog.showdialog(); not showing the print dialog in windows 7 with 64 bit

瘦欲@ 提交于 2019-12-01 15:51:02
I have custom control with print toolbar item.when print the control the dialog is not coming in windows 7 with 64 bit os in other system os working fine. problem only in windows 7 with 64 bit. my problem printdialog is not coming in windows 7 os with 64 bit. i have checked and anlyaed -->PrintDialog.ShowDialog() returns immeaditely cancel instaed of showing the dialog thats the problem. i have found the solution for the problem by searched following links: http://social.msdn.microsoft.com/Forums/en/netfx64bit/thread/8760fb6c-ae63-444e-9606-cd3295ce6b5d http://msdn.microsoft.com/en-us/library

Why does MSVC 2010 32bit project link to 64bit kernel32.dll?

 ̄綄美尐妖づ 提交于 2019-12-01 15:40:51
I have a Win32 (32bit) DLL project which builds and links without error. The DLL fails to load into a 32bit process. Using DependencyWalker, I see that the DLL is 32bit but has been linked with 64bit libraries for kernel32, msvcr100d, ws2_32 and msvcr100. DependencyWalker also shows an error Error: Modules with different CPU types were found. I've puzzled over this problems for a couple of hours now, and just can't fathom it - has anyone else experienced this, and found a solution? Short Answer: Use Dependency Walker for x86 for x86 stuff. Long Answer: Initially I used Dependency Walker for

printdialog.showdialog(); not showing the print dialog in windows 7 with 64 bit

夙愿已清 提交于 2019-12-01 15:40:09
问题 I have custom control with print toolbar item.when print the control the dialog is not coming in windows 7 with 64 bit os in other system os working fine. problem only in windows 7 with 64 bit. my problem printdialog is not coming in windows 7 os with 64 bit. i have checked and anlyaed -->PrintDialog.ShowDialog() returns immeaditely cancel instaed of showing the dialog thats the problem. i have found the solution for the problem by searched following links: http://social.msdn.microsoft.com

Error building 32-bit OS X app?

只谈情不闲聊 提交于 2019-12-01 15:22:05
问题 I'm working on my first Mac OS X app. My project was set-up with XCode defaults and I haven't touched any Build Settings. When building for Mac 64-bit, the app runs fine. However, when building for Mac 32-bit, I get a seemingly arbitrary error that says: Semantic issue: Synthesized property 'myProperty' must either be named the same as a compatible ivar or must explicitly name an ivar. What kind of things can I check for? 回答1: It sounds like you have found the error but I think I can answer

Java : switching between dll depends on system architecture (32/64)

孤街醉人 提交于 2019-12-01 13:52:56
I have a Java program uses some dlls. As these embeded dlls have to be built for a specific system architecture (32 or 64bits) I want to make a method/something that allow my program to switch between 32/64 bits version of dlls (or disable the library load if the program run on a 64 bits system) I hope there is a solution different from making two versions of the program Thanks in advance, Damien Use system properties: if ("x86".equals(System.getProperty("os.arch"))) { // 32 bit } else if ("x64".equals(System.getProperty("os.arch"))) { // 64 bit } You can use the System Property sun.arch.data

Android JNI: 32-bit compatability with 64-bit devices?

半城伤御伤魂 提交于 2019-12-01 13:07:44
I have some libraries that use native components, the libraries are built with NDK for 32 bit Arm architectures. now we have 64-bit processors on modern devices, so I'm wondering if the libraries will work. In my situation, I don't have the source code files of the native library, just the SO files, I can't build them for 64-bits. So will the 32-bits libraries run on 64-bits processors? or I have to re-build them? ** EDIT ** In my scenario I have the following: 1- I distribute the APK manually, didn't publish to Google Play yet. 2- The project has two native libraries, one with 64 & 32-bits