WIX安装程序覆盖ServiceInstaller配置是否为默认行为？该类作用何在？

Question: #

I'm developing a service that will be deployed via a WIX installer. Here's my service installer class code:

this.ServiceInstaller.DisplayName = "My Service";
this.ServiceInstaller.ServiceName = "MyService";
this.ServiceInstaller.ServicesDependedOn = new string[] { "ServiceA", "ServiceB", "ServiceC"};

And here's my WIX installer code:

<Component Id="MyService.exe" Guid="{1234}">
  <File Id="MyService.exe" KeyPath="yes" Source="$system\$(sys.BUILDARCH)\MyService.exe">
    <netfx:NativeImage Id="MyService.exe" Platform="all" Priority="1" />
  </File>
  <ServiceInstall Id="MyService.exe" DisplayName="My OTHER Service" Name="MyService" ErrorControl="normal" Start="auto" Type="ownProcess">
    <ServiceDependency Id="ServiceD" />
    <ServiceDependency Id="ServiceE" />
    <ServiceDependency Id="ServiceF" />
    <util:ServiceConfig FirstFailureActionType="restart" SecondFailureActionType="restart" ThirdFailureActionType="restart" RestartServiceDelayInSeconds="10" />
  </ServiceInstall>
  <ServiceControl Id="MyService.exe" Name="MyService" Stop="install" Remove="uninstall" />
</Component>

After troubleshooting, I found that the WIX configuration completely overrides the settings in the project's installer class (especially the service name and dependencies). Is this the default behavior? If WIX completely ignores the ServiceInstaller class configuration, what's the point of this class?

Answer: #

Great question—this is totally expected default behavior, and it boils down to how WIX and .NET's installer classes interact with Windows Installer. Let me break this down clearly:

1. Yes, WIX ignoring ServiceInstaller is default behavior
   WIX builds a native Windows Installer (MSI) package directly, using the explicit configuration you define in your .wxs files. The .NET ServiceInstaller class is part of the "Installer Class" system, which relies on InstallUtil.exe to execute custom installation logic for .NET assemblies. By default, WIX doesn't run these installer classes unless you explicitly add a custom action to call InstallUtil (or use the InstallerClass attribute on your Component—though that's generally not recommended for services since WIX has native, more reliable support).

   When you use WIX's <ServiceInstall> element, you're directly telling Windows Installer how to register the service. This takes absolute precedence over any settings in your .NET installer class, because WIX isn't executing that class at all by default.

2. What's the purpose of ServiceInstaller then?
   The ServiceInstaller class was built for the traditional .NET service deployment workflow that doesn't use WIX or other dedicated MSI authoring tools. Here's where it shines:

   • If you're deploying your service using InstallUtil.exe (e.g., running InstallUtil MyService.exe from the command line), this class defines all critical service registration details—display name, dependencies, startup type, and more.
   • It’s useful in custom deployment scenarios where you need programmatic control over service installation (like a custom setup EXE that handles logic outside of standard MSI capabilities).
   • If you want to reuse settings between WIX and your installer class, you could extract common configuration (service names, dependencies) into a shared file (like a constants XML or .NET resource) and reference it in both places—but WIX won't automatically pick up ServiceInstaller settings on its own.

   A quick best practice note: It’s generally smart to pick one approach for service registration—either let WIX handle it via <ServiceInstall>, or use the ServiceInstaller class with InstallUtil. Mixing both can lead to confusing conflicts and hard-to-debug behavior, which sounds exactly like what you encountered here.

内容的提问来源于stack exchange，提问作者Danw25