> What I want to know is; do all shell executed .NET app run in the same
> process? For that matter do all runtime-hosts run all of their
> app-domains in the same process?
>
> In the case of a shell executed application here's my understanding:
> Double clicking a .NET executable file invokes a runtime host
> specifically for running user space apps (by which I mean services,
> exe's - not hosted by IIS, SQL Server or anything else).
>
> This runtime-host creates an app domain, loads the application's
> primary assembly and kicks it off at the entry point. Referenced
> assemblies are loaded at the point at which they are first needed. So
> is this runtime host an ever present process on my machine? Is there a
> limit to the number of add domains it can support?
>
> Here's another thing, I also read:
>
> "There is not a one-to-one correlation between application domains and
> threads. Several threads can be executing in a single application
> domain at any given time"
>
> OK
>
> "and a particular thread is not confined to a single application
> domain. "
>
> eh?
>
> "That is, threads are free to cross application domain boundaries; a
> new thread is not created for each application domain."
>
> So is the run-time host playing scheduler for a predefined number of
> threads switching them between app domains?
>
> Thanks to anyone who can shed some light
>