0x64 to 0x86 serialisation issue

[bzburr]

Hi I'm building a solution with two projects - the Client is a 8x64 project and the Server is 0x86 When i send a message across to the server there is a serialisation problem

The thread 0x210c has exited with code 0 (0x0). The thread 0x2134 has exited with code 0 (0x0). 'MyCaller.vshost.exe' (CLR v4.0.30319: MyCaller.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Accessibility\v4.0_4.0.0.0__b03f5f7f11d50a3a\Accessibility.dll'. Symbols loaded. 'MyCaller.vshost.exe' (CLR v4.0.30319: MyCaller.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\UIAutomationProvider\v4.0_4.0.0.0__31bf3856ad364e35\UIAutomationProvider.dll'. Symbols loaded. Exception thrown: 'System.IO.FileNotFoundException' in mscorlib.dll Exception thrown: 'System.IO.FileNotFoundException' in mscorlib.dll Exception thrown: 'System.IO.FileNotFoundException' in mscorlib.dll Exception thrown: 'System.Runtime.Serialization.SerializationException' in mscorlib.dll

when i build both systems in 0x86 everything works just fine and messages go back and forth as expected.

For background information -I am using named pipes betwen 0x64 and 0x86 to control a 0x86 COM object that cannot be rewritten in to 0x64

What modifications do i need to make to make this serialisation issue work?

Buzz

[hornms]

I used NamedPipeWrapper for this same purpose (not COM object, but 32-bit DLL). The serialization I chose is simple strings of JSON. I routinely pass 10-100 MEG of serialized JSON using this pipe. Try this kind of serialization to see if it meets your needs.