Is CLR loaded and initialized everytime, when a new managed application is loaded and there is a managed application already present?
e.g. If on my machine, application "TestApp" is running and after that I start another application "DemoApp". In this case, wiill CLR be loaded again for DemoApp? Or it will use the same one which is loaded by TestApp?
Yes, and assemblies are JIT compiled, heaps are allocated and so forth. The Windows image loader will help a bit but in general the CLR overhead is per process.
CLR is not fully loaded every time. The article linked below mentions a "hot startup" scenario, when the CLR is ready. You may have noticed this yourself when you start a .NET app for the very first time after system startup.
In the warm startup scenario (for instance, you have already run a managed application once), it is likely that most of the pages for the main common language runtime (CLR) components are already loaded in memory from where the OS can reuse them, saving expensive disk access time. This is why a managed application is much faster to start up the second time you run it. These soft faults dominate warm startup.
来源：https://stackoverflow.com/questions/3245791/is-clr-loaded-and-initialized-everytime-when-a-new-managed-application-is-loaded