If dedicated app pool option is set in web policy, but neither .NET framework option is enabled in a hosting plan, then website creation in spaces using that hosting plan fail at creating the application pool. I suppose, because no .NET CLR version is available to bind to. However, IIS allows to create app pools with "no managed code" CLR setting, so from IIS side it's possible what we want to achieve.

We have some free (+ some very cheap) PHP+MySQL only plans, which we would like to disable .NET for, but still want to run these sites in their own pool. We enabled .NET 1.1. which kinda works because no one use it any more practically, but it would be cool if SolidCP would add support for this scenario. E.g., if there is no available/enable CLR version, it would create the app pool with "no managed code".