Kbase P183638: OEA: Error "Not a valid assembly" adding a 64-Bit assembly using the Assembly References Tool (proa
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/03/2011 |
|
Status: Unverified
SYMPTOM(s):
OEA: Error "Not a valid assembly" adding a 64-Bit assembly using the Assembly References Tool (proasmref)
Assembly built by Visual Studio on a 64-Bit Windows 7 platform using Visual Studio default build settings
FACT(s) (Environment):
The Assembly References Tool (proasmref) successfully adds assemblies built using the Visual Studio "Any CPU" option.
Windows
OpenEdge 10.2x
CAUSE:
Building assemblies on Windows 7 64-Bit platforms generate 64-Bit DLL files by default. OpenEdge uses a 32-Bit Java Virtual Machine (JVM) and 32-Bit .DLL files to load the assembly information. If the assembly is compiled to as pure 64-bit, the Assembly References Tool (proasmref) cannot add it.
FIX:
To successfully use the OpenEdge Assembly References Tool (proasmref) to add custom assemblies to your OpenEdge Project, build your assemblies using the Visual build for "Any CPU" option. Using this option will JIT to 64 bit code when loaded into 64 bit process and 32 bit code when loaded into a 32 bit process.