[Mono-dev] PATCH: Make Process.Start() use thesame'mono'runtime
2a5gjx302 at sneakemail.com
Thu Jun 7 16:24:20 EDT 2007
At 02:21 PM 6/7/2007 +0200, Manfred F. Braun wrote:
>Hi All !
>Sorry for my 2 cents.
>I am working a lot with processes, both, native as .net related, mostly
>under windows, but will be able to keep my code running on both worlds.
>What I always expect is, a process is a process, nothing else. Which runtime
>runs inside the process is up to the starter of the process. Usually, I
>start windows executables, with and without GUI. Even if I start a .net
>executable, which is handled by the windows shell to span a new runtime,
>that is excactly, what I want to do. The spawned processes should keep
>running, even my starter terminated in the meantime. A process is a stronger
>isolation level that an appDomain, so I use this for a lot of reasons. If I
>need to communcate with the spawned app, I use remoting.
>I would never expect to run a new .net executable in the sampe process.
>As I said, these are just my 2 cents.
Nobody is currently considering making Process.Start not actually start a
process. It was suggested briefly but contemplation of the matter
immediately brings forth a slew of reasons that it is entirely a bad idea.
For example: What process ID would the resulting Process object return?
What would happen if you called .Kill on it? A Process does not wrap an
AppDomain, plain and simple, and people who want the performance benefit
that might be possible by executing the assembly in a child AppDomain
instead of a separate process are free to use AppDomain.ExecuteAssembly.
More information about the Mono-devel-list