InstallAware

I know, that sort of goes against the "saving space with 7zip" thing.

But then, really, sometimes you distribute your stuff by cd and do not care. PLUS, a dotnetfx.exe can be installed manually external of the core setup.

Would be nice if, sort of in addition to the current mode, web-blocks made by repackaging could instead use the original.

Hi Thona

If dotnetfx.exe is installed externally, it won't be re-installed by InstallAware - so that saves the potential download that would incur if web media blocks were used (and in any other build mode - uncompressed or single file - a dynamic download wouldn't happen anyways).

You can also, by touching up your setup script, or even the default runtime installation include files (so you don't have to keep doing it over and over again for each setup), replace the default mechanism with a new one that downloads the default FX file from the Microsoft web site, and runs it - silently or not - when a FX installation is needed.

So I think you're covered...honestly I don't see a need to replace the default mechanism here in the template setups - that would only confuse users, would it not? Why would we offer them two choices and make them choose, when its not even clear why they need the second choice?