Game Development Reference
You can instantiate this class after your form exists and call AssignHandle() on the
NativeWindow instance, passing in the Handle property of your form instance.
This chapter started off by discussing what inter-process communication is and
why it is important, and then described some IPC mechanisms that are native to
Microsoft.NET, and then some IPC mechanisms that are only available through
Platform Invocation Services. Remoting was briefly covered, but nowhere near
close to the level of detail that is available from topics that are dedicated to the sub-
ject. I recommend that you pick up the topic Advanced .NET Remoting by Ingo
Rammer (ISBN: 1590590252) if you want to investigate this awesome technology
in greater detail.
A large number of IPC mechanisms were at least briefly covered in this chapter, though
some were left out since the chapter is generally directed towards WM_COPYDATA .
Some excluded IPC mechanisms are shared memory spaces and overlapped I/O.
Be sure to check out the Companion Web site for a robust library that wraps and
manages communication between managed and unmanaged applications, includ-
ing an example that shows library usage. There are two flavors of the library: one
for managed applications and one for unmanaged applications. This library allows
you to group messages into channels, so that you can perform filtering or classifi-
cation of messages and associated data.