One is 64bit, the other is 32bit. I'm currently doing it while making the 32bit app console, and reading the output. Is there a better way? My data is text.
EDIT: Both executable are on the same machine.
Asked
Active
Viewed 2,274 times
3
-
Can you just compile the 64 bit app as x86 and have a single process? – David Heffernan Dec 18 '11 at 13:57
-
In other words the 32/64 part of your question doesn't actually matter. The real issue is that you need to have communication between two distinct processes. – David Heffernan Dec 18 '11 at 13:58
-
Well, of course it will be better if I'm somehow able to merge them both into one. – blez Dec 18 '11 at 14:00
-
What is stopping you merging? – David Heffernan Dec 18 '11 at 14:10
-
How to merge them if and run the 32bit from 64bit environment? – blez Dec 18 '11 at 14:12
-
Can you explain why you can't use 32 bit throughout? If you can then a single process would likely be easier. – David Heffernan Dec 18 '11 at 14:16
-
See Related questions list on the right side of this page. There are several topics that are similar to your question. – Eugene Mayevski 'Callback Dec 18 '11 at 16:02
3 Answers
1
If you are constrained to .NET 2.0 then there are a few ways you can do it:
- if the two apps are on different machines, you can use sockets, or .net Remoting (depending on the complexity of interaction)
- if the two apps are on the same machine, .net Remoting is an ok choice.
The fact that they are 32 or 64 bit does not influence this in any way.
Tudor
- 61,523
- 12
- 102
- 142
-
@blez: Then I suggest .Net Remoting. It allows you to call methods directly from one program to another. – Tudor Dec 18 '11 at 13:55
-
-
@blez: On the same machine I think it uses shared memory. You can specify which underlying mechanism you want to use. – Tudor Dec 18 '11 at 13:58
0
In .NET 2.0 you could use Remoting.
Darin Dimitrov
- 1,023,142
- 271
- 3,287
- 2,928
-
-
@blez, yes, it can be blocked. You could use a port that is in the exceptions of the firewall. – Darin Dimitrov Dec 18 '11 at 13:57
-
-
-
@blez, as far as I know, named pipes in .net 2.0 can only be used by calling the native Win32 pipe API. Like I said, remoting can also use shared memory if you're on the same machine. – Tudor Dec 18 '11 at 14:04
-
@DarinDimitrov Out of curiousity: Is the IPCChannel class really using sockets that can be blocked by a firewall? – yas4891 Dec 18 '11 at 14:07
-
@yes4891: It does not use sockets. From MSDN: "Because it does not use network communication, the IPC channel is much faster than the HTTP and TCP channels, but it can only be used for communication between application domains on the same physical computer." – Tudor Dec 18 '11 at 14:58
-
@Tudor: It looks like it's actually using sockets. Cause one example I tried blocks 8080, which is used by another app. – blez Jan 08 '12 at 14:33
