I'm currently trying to automate the installation procedure of ASP.NET Core Hosting Bundle. It is going to be a setup which first starts the Setup of the Bundle which the user has to click through and then enables IIS. Since the application that this setup installs and is later hosted by the IIS, is built as a self-contained app, I couldn't care less about the runtime and whatnot, but I need the AspNetCoreModuleV2 to be installed.
My Problem is, on all my test systems where I tested it, I cannot get it to install the module reliably. Sometimes it get's installed directly, sometimes only after restarting the .NET Core Setup and hitting repair.
This is true for systems that have seen previous installs of the ASP.NET Core Hosting Bundle, but also system that im fairly certain (but not sure) haven't.
I was looking into cleaning up all references to the module, but after uninstalling the bundle, deleting all the folders, deleting registry entries, and cleaning it from the IIS Config file (yes the uninstallation didn't touch any of these), it seems that the setup still picks it up somewhere and then just doesn't install it.
I really don't want to look around the whole system just to check if the module was installed correctly or not, and I also don't want to double-prompt the user with the installation of the hosting bundle.
Since the module consists of a single file, at least from what I found so far, could I just redistribute the .dll, copy it to where it should be and add the reference to it in the IIS config file by myself?
Or can I get the installer to full-install the hosting package no matter what's on the System?