From dbde1ebffbfc3205fce92ba5e9b0551954e6f9f2 Mon Sep 17 00:00:00 2001 From: Felipe Zipitria Date: Sun, 26 Jul 2026 10:57:36 -0300 Subject: [PATCH] fix(iis): correct InstallModule32/64 CustomAction ID naming swap In the 64-bit installer (Win64=yes), the CustomAction IDs were swapped relative to what they actually install: "InstallModule32" installed the 64-bit module (System32, bitness64 precondition) and "InstallModule64" installed the 32-bit one (SysWOW64, bitness32 precondition). Not a functional bug: both actions run unconditionally on every install and are correctly gated by appcmd's own /preCondition bitness check rather than by the CustomAction ID, and the InstallExecuteSequence references already matched their (mis-)named actions consistently. But the naming makes the file misleading to maintain, and inconsistent with the already-correctly-named UninstallModule32/64 pair. Rename only, no logic/order change: swap the two CustomAction Ids and update the matching InstallExecuteSequence "Custom Action" references so each ID now matches its actual bitness, in the same relative order as before. Found while reviewing #3491. Signed-off-by: Felipe Zipitria --- iis/installer.wxs | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/iis/installer.wxs b/iis/installer.wxs index 18b2d1cbf..26a31b65b 100644 --- a/iis/installer.wxs +++ b/iis/installer.wxs @@ -361,9 +361,9 @@ - - - + + + @@ -390,8 +390,8 @@ - - + +