SimpleIPCExpress lets you have some of your application's work performed in an external process on the same machine - insulating your app from memory leaks and process crashes. You make function calls to objects in the external process as if they were local objects. Under the covers you're using .NET Remoting over the IPC (Inter Process Communication) channel, but you don't need to be an expert on .NET Remoting to use SimpleIPC. The platform handles the communications and process life cycle details for you. SimpleIPC runs on Windows, and the code to be run in the external process must be written in a .NET programming language. However, your client code may be written in a variety of languages, to include Java, VBScript/VBA, and .NET languages. You might consider using SimpleIPC under the following circumstances: 1. You have some code which is useful, but which has the potential to throw unhandled exceptions and crash your application process. You can run this code via SimpleIPC. If there is a process crash, it will be one of the expendable external processes, rather than your application process. Your application can just repeat the call against a different external process and continue on. There is no need for your end users to be impacted. 2. You have some code which is useful, but which leaks memory. You can run this code via SimpleIPC and configure the external processes to recycle frequently. In this way, you can keep your application's memory consumption under control without sacrificing functionality. 3. You need an expeditious way to perform one of several common programming tasks, such as invoking .NET code from a Java application, running a subset of your application's operations under a different Windows identity, or limiting concurrent access to shared resources in a multi-user environment. SimpleIPC provides simple APIs for programming tasks like object pooling and invoking web services. 4. You need to add multithreading to an MS Office app.