Installation order of prerequisites and Windows features

[rmoc]

I have a tricky problem regarding the installation order of prerequisites and Windows features. My software is based on ASP .Net Core 8 and is hosted as a website within IIS. I therefore install the ‘ASP.NET Core Hosting Bundle 8.0.16’ and the Windows feature ‘IIS’. After installation, the website does not work because Microsoft requires that the hosting bundle be installed after IIS (or repaired if already installed, see https://learn.microsoft.com/en-us/aspne ... etcore-8.0). When I try to run the hosting bundle as a custom action (LaunchFile) after ‘InstallIIS’, I run into the MSI restriction that only one installation can run at a time.

Unfortunately, the repair in step 3 (as After Main Package) does not work either, as I have to modify the website with a custom action, which in turn requires a valid ASP NetCore Bunde installation.

order.png (19.98 KiB) Viewed 740 times

Currently, I can't find a solution to the problem other than specifying an already installed IIS as a prerequisite for my software. However, I don't find this particularly customer-friendly and would like to avoid it. Perhaps someone has an idea on how to solve this problem.

Thanks in advance.

[Catalin]

Hello Rene,

The same issue has been discussed in this thread:

.NET Core Hosting Bundle with IIS

Could you please have a look over that and let me know if it helps?

Best regards,
Catalin

[rmoc]

Hello Catalin

Thanks for your reply. The workaround isn't ideal. Regardless of the fact that I have to activate IIS via script even though the feature is available in AI. But the main problem is probably that the workaround doesn't work without a UI. I think I'll have to come up with something else here.

Regards
René

[Catalin]

Hello René,

You are always welcome!

I'm sorry to hear the workaround is not ideal for you. Unfortunately, I'm afraid I'm not aware of another solution for this (maybe a repar triggered by a custom action after the installation).

I think I'll have to come up with something else here.

If you manage to find anything besides the two already knwown workarounds, please let us know, as that might be useful for other customers in the future.

Best regards,
Catalin