1

Topic: How to create new process?

How to create controlled (managed) process without having exe-shnika? I.e. not to specify in Process. Start or its parameters any executable file from a disk. It is necessary for me that that process had a heap. I will create in it object,  with it and through it I will use. And when I will cease - process will be completed also all its heap at once .

2

Re: How to create new process?

Hello, Ejnstok Fajr, you wrote: > How to create controlled (managed) process without having exe-shnika? > I.e. not to specify in Process. Start or its parameters any executable file from a disk. > It is necessary for me that that process had a heap. I will create in it object,  with it and through it I will use. > And when I will cease - process will be completed also all its heap at once . Probably, code start in the separate domain approaches: https://docs.microsoft.com/ru-ru/dotnet … ion-domain

3

Re: How to create new process?

The C> approaches code start in the separate domain Is not present. At all domains of one process the general heap. And the heap separate is just necessary to me. And so yes, the domain would approach. But does not approach.

4

Re: How to create new process?

Hello, Ejnstok Fajr, you wrote: > How to create controlled (managed) process without having exe-shnika? > I.e. not to specify in Process. Start or its parameters any executable file from a disk. And in what a problem to have separate WorkerProcess for such purposes? Why there was a requirement "without having exe-shnika"? > it is necessary for me that that process had a heap. I will create in it object,  with it and through it I will use. > And when I will cease - process will be completed also all its heap at once . Besides - why so? Why it is impossible to clean a heap simply? Since I do not know, what exactly you want to receive, I can try to assume that probably you will accept start of one more CLR Runtime in the same process (like as it probably). Try to look here Hosting (Unmanaged API Reference) But as on me is too  (and not the fact that implementablly generally - it is quite probable that there is a restriction on number of hosts within the limits of one process).