Running designer on a 64bit plattform throw up error
Posted: Thu Jan 21, 2010 3:50 am
Hello
the following problem was noticed by me: When running .Net Applications in 64Bit Mode there is a unhandled exception when calling the Designer out of the code in the 2009.3 version. The mainly problem seem to be, that Microsoft is not providing a 64Bit Version of Microsoft.JET Engine, which is initiated through the designer on callup.
The error message of the exception say's at general this: " Could not load Microsoft.Jet Enginge".
Since the Jet-Engine will not be available in a 64bit Version, and you can't load a 32bit interface out of a 64bit Process, is there any possibility to recognize that the .Net Process is running in 64bit mode and, then, prevent loading of the Microsoft.Jet Engine through the Designer ?
The first work around is to compile the Application not for the target environment "All Processor Type's" but for "Only 32-bit compatible systems" resulting in running as 32bit application on a 64bit operating system (then, it can load the 32bit interface of the JET-Engine).
This is a first workaround, but it would for sure be nice if you can run a .Net Application with a Designer on both platforms nativly.
Anyone experiences with this ?
P.S.: For all other: Please recognize that, if you have not hard-compiled for a 32bit environment and use the normal setting of all platforms as target, your application would run in 64bit, too, if it is moved or installed on a 64bit Operating System. Then you would experience the same error in calling up the designer.
With greetings!
the following problem was noticed by me: When running .Net Applications in 64Bit Mode there is a unhandled exception when calling the Designer out of the code in the 2009.3 version. The mainly problem seem to be, that Microsoft is not providing a 64Bit Version of Microsoft.JET Engine, which is initiated through the designer on callup.
The error message of the exception say's at general this: " Could not load Microsoft.Jet Enginge".
Since the Jet-Engine will not be available in a 64bit Version, and you can't load a 32bit interface out of a 64bit Process, is there any possibility to recognize that the .Net Process is running in 64bit mode and, then, prevent loading of the Microsoft.Jet Engine through the Designer ?
The first work around is to compile the Application not for the target environment "All Processor Type's" but for "Only 32-bit compatible systems" resulting in running as 32bit application on a 64bit operating system (then, it can load the 32bit interface of the JET-Engine).
This is a first workaround, but it would for sure be nice if you can run a .Net Application with a Designer on both platforms nativly.
Anyone experiences with this ?
P.S.: For all other: Please recognize that, if you have not hard-compiled for a 32bit environment and use the normal setting of all platforms as target, your application would run in 64bit, too, if it is moved or installed on a 64bit Operating System. Then you would experience the same error in calling up the designer.
With greetings!