[wix-users] Better way to install IIS features than DISM

[Herman van Drie]

You could always create an Wix CA yourself and call DISM API.

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism/dism-api-reference?view=windows-11
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism/dismenablefeature-function?view=windows-11

It's how I created various custom CA's that uses tables/properties for input.

That's how I would do it.

Cheers,

Herman van Drie

-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Bevan Weiss via wix-users
Sent: dinsdag 23 november 2021 01:08
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Bevan Weiss <bevan.weiss at gmail.com>
Subject: [wix-users] Better way to install IIS features than DISM

Hi all,
I've currently got an installer which has been working well for a number of years, it was a bit kludged together at the time, but hasn't been responsible for any fires, so it's survived reasonably untouched.

It is however using DISM for IIS installation / configuration under Windows Server (both WS2012R2 and WS2019 have been targeted so far). Currently this ends up looking like a couple of calls to the PlatformQuietExec CustomAction with commands like '"$(var.DISM)" /online /enable-feature /FeatureName:IIS-StaticContent .... /All'
This is working fine, however two of these commands are longer than they should be and generate ICE03 warnings.  They still appear to work, but ultimately it means that I'm not really doing things the right way.  And if I'm going to change it, then I should just do it the right way.

I've done some googling, and there's a number of variations, but they do seem to all come back to just calling DISM.  Is there a better way that I'm missing?

Regards,
Bevan Weiss

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/