Allow phonetic typing
I have an application that works perfectly on all versions of Windows that are 32 bit. In the application to use the Dev Express v8.3 controls. When I try to start the application on x64 win 7 shooting in the old and see that there is a problem with reading a common-dll containing refernce to devexpress.- Bad image exception. Is there any idea of how effectively they can solve the problem?
You should really ask DevXpress if that old version of their library fully supports x64 machines or not.
In general pure .Net managed code does work well on all supported CPU architectures as IL is compiled by the jit compiler at runtime.
Your bad image f. error is surely related to cpu architecture issues but are you 100% sure is from one of the devxpress files?
Related
I am considering to learn Ada. I found several resources online, and Programming in Ada 2012 by Barnes is on its way to here, so that should get me started.
The target machines for the future Ada programs are Intel 64 bit, and the target OSes are Win 8.1 and Win 10.
However, I was not able to find an example on how to interact with the Windows API in order to draw and manipulate Windows. Could someone please direct me to a source, so that I can have a look at how such code would look like?
Also, all I've read so far indicates, that Ada compiles only 32 bit executables for Windows. Is it correct that I can not generate true 64 bit Windows programs?
The recent GNAT community release does target 64bit. An alternative is TDM-GCC which has provided a GNAT release targeting 64bit for a while.
There is Win32Ada which is a binding to the Windows API. However, I don't think it has been updated with new APIs of Windows 8.1 or Windows 10. However, you can always import functions from the Windows API into Ada yourself.
There is GtkAda which allows you to use GTK to create GUIs. However, these are not „native“ Windows GUIs.
We're in the unfortunate situation of still having to support a Windows CE based device (ARMV7 architecture). We're continuously running into problems regarding the limited functionality of .NET Compact framework (no security libraries, very limited asynchronous support, ...). Since the .NET Core CLR has been compiled for multiple platforms, including ARM-based platform, the idea of trying to compile it for Windows CE as well came up. I invested about a day to see how far I'd get, however I'm not the most experienced CMake user.
I couldn't find any hint on the internet whether someone ever tried, so... Is there a basic possibility of succeeding in doing so or are there limitations I do not yet see which make getting a working version highly improbable?
I want to start learning Qt for developing GUI's, and I'm trying to decide between the old Qt (not QtQuick1) and QtQuick2. I was hoping to use QtQuick2, but I'm confused about the opengl issues with Windows XP. My question is, will it be possible in Qt 5.4 to deploy a QtQuick2 GUI to Windows XP, without requiring the user to update any drivers? If not, are there any plans to make that possible in a future version of QtQuick?
edit: I know that Windows XP is really really old, but a lot of my potential customers are still using it.
On WinXP, prefer the ANGLE build of Qt5, which uses OpenGL ES over Direct3d instead of OpenGL. If you have customers using WinXP, then it's more than likely that they have never updated their drivers, which will cause problems for QtQuick.
I am sure you can not expect any improvements for Windows XP. DO NOT use XP anymore. Generally Qt5 has only very restricted XP compatibility (http://qt-project.org/doc/qt-5/supported-platforms.html).
If you want to start learning Qt you should use the newest Qt but you should drop Windows XP.
Summary
To get my site running smoothly on a 64bit server platform, using IIS 7.0 Integrated pipeline mode, what are the things I would need to fix in order for this to work.
Some more detail
I am aware of, that if a assembly uses PInvoke and I have a reference to such a assembly in my project, the error message I will get will probably be very vague and obscure.
How do I go about finding these assemblies?
If I look at a dll, with reflector, and there is no PInvokes, would this be sufficient to assume that the dll, would be fine in a 64 bit environment?
Any specific suggestions on how to check that my site is fully 64 bit compatible? Would compiling it as AnyCPU be sufficient to ensure that it will run correctly in Integrated pipeline mode?
Thanks
Rihan
We have found the offending dll, buy a process of elimination. So sadly I cant offer a more "scientific" approach.
What I have learned through this process:
Be careful when selecting 3rd party libraries
Especially when it is just a "proof of concept"
Before you know it, that code is in production, and you spend a week trying to find that one library that is causing problems.
You probably wont have to deal with this issues, but developers that come after you will have less respect for you.
If I want to run a program in windows PE (Vista or 7) am I not allowed to use any level of managed code?
Can I only have c++ code that doesn't reference any dotNet code?
How can I interact with windows? Do I have to use user32.dll type files to carry out various operations?
Edit: See also Can Windows PE 2.0 support the .NET framework?
Windows PE is a very limited bit of windows before windows proper. It stands to reason that vast parts of the windows in the WIN32 subsystem will not be available. However this page discusses coding with PE (though its limited to XP embedded). And this discusses some ui aspects under PE and possibly ways of getting access to the windows libraries.
It may be possible to self host the CLR but I doubt it. Might make an interesting challenge. Let us know how you get on.