out-of-process possibilities

[Jeff Beem]

My company uses a 3rd party ActiveX control that has presented us with a
number of memory corruption issues The control is critical to our
application and the provider of the control is very slow in fixing issues.

To combat the problem we started hosting their control in an ActiveX EXE so
that it would run in a separate process space and not corrupt the memory of
the main application. Of course, this was all in VB6. We're now using .NET
and would like very much to rid ourselves of ActiveX EXEs, but the memory
corruption issues remain.

So my question is... is there a way to create an assembly that runs in a
separate process space, similar to an ActiveX EXE? Or are there other ways
we could run the 3rd party control and protect the memory of our application?
Any help would be greatly appreciated.

Thanks

[John A. Bailo]

You can use remoting to create such a process.

Or you can even use a web service, depending on the nature of what the
ActiveX control provides.

You many also want to look at Indigo (WCF) for easier implementations of
remoting...but it's all doable with .NET 1.1
Jeff Beem wrote:

My company uses a 3rd party ActiveX control that has presented us with a
number of memory corruption issues The control is critical to our
application and the provider of the control is very slow in fixing issues.

To combat the problem we started hosting their control in an ActiveX EXE so
that it would run in a separate process space and not corrupt the memory of
the main application. Of course, this was all in VB6. We're now using .NET
and would like very much to rid ourselves of ActiveX EXEs, but the memory
corruption issues remain.

So my question is... is there a way to create an assembly that runs in a
separate process space, similar to an ActiveX EXE? Or are there other ways
we could run the 3rd party control and protect the memory of our application?
Any help would be greatly appreciated.

Thanks