Hello Brian,
thanks for your reply.
For me, remoting always was a call on a business component that will
do something, return a value and then is gone.
What I am looking for is a component with a windows front end or let's
say a windows application with an external control inteface. This
application should stay alive as long the calling application has a
link to it.
For me it is not clear if this will still be the right way.
If yes, should I write my own hosting application or use IIS?
Thanks in advance.
Best regards
Ulrich
"Brian Gideon" <br*********@yahoo.com> wrote in message news:<11*********************@g14g2000cwa.googlegr oups.com>...
Ulrich,
You can use .NET Remoting to allow two processes to talk to each other.
This is not the same thing as out-of-process components in VB6, but it
should provide you with the functionality you desire. Also, take a
look at application domains (the AppDomain class) for more isolation
options.
Brian
Henne wrote: Hello,
in VB6 we werr able to make ActiveX-DLL's (In Process Components) and
ActiveX-Exe (Out Of Process Components).
Out Application is build of one main application that starts other
modules. These modules are ActiveX-Exe's. The main application
controls the modules via ActiveX.
We decided to use ActiveX-Exe because we want to run the modules in
separate processes. So when one module crashes the others are still
available.
Now we want to migrate to .NET.
How can I create a "Out of Process" component with .NET.
When I call a method of a .NET class library, these component always
runs in the same process as the calling application.
Any ideas?
Thanks in advance.
Best regards,
Ulrich Henne