Maybe I can better explain myself. A program like paint.net is a program that normally would be "installed" on a "fully installed" OS. The fact that it uses t

Maybe I can better explain myself. A program like paint.net is a program that normally would be "installed" on a "fully installed" OS. The fact that it uses the .Net subsystem is mostly "transparent" (to be picky it is transparent on recent OS's where the .Net subssystem is installed anyway, not so much on older systems where .Net is not installed or is installed by default in an earlier version that may not be compatible with the program at hand and needs an update). For it and for any number of programs that only make sense on a full system this is not an issue at all. The allergy I declared revolves about small tools that would be useful both in a fully installed system and in a reduced environment, such as a PE or RE (Pre-installation Environment or Recovery Environment) typically used in recovery or repairing scenarios, typically booting from removable media such as a USB stick or CD/DVD . In these cases it is more complex (and anyway adds several tens of megabytes to the build, which implies also often slower booting) to have a working .Net environment suitable to run the given program/tool.