Why WIX MSI for ASP.NET is installing website in "C:\Program Files" folder instead of "c:\inetput\wwwroot"?

[edgarsad007]

Question

Wix installer MSI is installing files in folder: "C:\Program Files\MyManufacture MyWebsiteName" and creating empty folder: "C:\inetpub\wwwroot\testwebsite". Visual Studio 2022, WIX version is 5.0.2. Here is Package.wxs:

`
< Wix xmlns="http://wixtoolset.org/schemas/v4/wxs"
xmlns:iis="http://wixtoolset.org/schemas/v4/wxs/iis">
<Package InstallerVersion="200" Compressed="yes"
Manufacturer="MyManufacture" Version="1.0.1.0"
Name="MyWebsiteName" UpgradeCode="GUID4C5B-B0C3-43FD-82A2-9F347D66CC7B">
<MajorUpgrade DowngradeErrorMessage="Downgrade Error" />
<MediaTemplate EmbedCab="yes" />
<StandardDirectory Id="TARGETDIR" >
<Directory Id="INETPUB" Name="Inetpub">
<Directory Id="WWWROOT" Name="wwwroot">
<Directory Id="INSTALLDIR" Name="testwebsite"/>
</Directory>
</Directory>
</StandardDirectory>

<iis:WebSite Id="TARGETSITE" Description="My Website" Directory="INSTALLDIR">
  <iis:WebAddress Id="WebAddress1" Port="80" />
</iis:WebSite>
  <Component Id="ProductComponent" Guid="GUID4C5B-B0C3-43FD-82A2-9F347D66CC7B">
    <iis:WebVirtualDir Id="MyWebApp" Alias="MyWebApp" Directory="INSTALLDIR"
    WebSite="TARGETSITE">
      <iis:WebApplication Id="TestWebApplication" Name="Testappl" />
    </iis:WebVirtualDir>
  </Component>

<Feature Id="ProductFeature" Title="titleoffeature" Level="1">
  <ComponentGroupRef Id="MyFiles"/>
  <ComponentRef Id="ProductComponent"/>
</Feature>

<ComponentGroup Id="MyFiles" >
  <Files Include="..\MyWebsiteFiles\bin\$(Configuration)\publish\**" />
</ComponentGroup>

`

If I add a Directory to ComponentGroup:

<ComponentGroup Id="MyFiles" Directory="INSTALLDIR">

then there are a lot of error for all files like this one:
The component 'flsgddXcR6nNmV92KPFD8bN4scNbFI' has a key file with path TARGETDIR\inetpub\wwwroot\testwebsite\appsettings.development.json'. Since this path is not rooted in one of the standard directories (like ProgramFilesFolder), this component does not fit the criteria for having an automatically generated guid. (This error may also occur if a path contains a likely standard directory such as nesting a directory with name "Common Files" under ProgramFilesFolder.)

Why website is installed in "C:\Program Files\MyManufacture MyWebsiteName" folder instead of folder "c:\inetput\wwwroot\testwebsite"?

Open Source Maintenance Fee

• I pay the Open Source Maintenance Fee by sponsoring the wixtoolset project because I support the maintainers.

[robmen]

1. The error message is long but pretty specific. You need to root your files in one of the StandardDirectories (like ProgramFilesFolder) for automatic Component GUID generation to create stable GUIDs. The part that is missing is that TARGETDIR is a strange directory because it will move around to be the drive with the most space on your computer, which can really wreck havoc with installers. So, it doesn't count... it's a special standard directory. We should probably update the error message to call out "not TARGETDIR".

2. By default, if you don't specify a folder for your stuff, it installs into INSTALLFOLDER which defaults to Manufacturer + Package Name. Note that it is rooted in a StandardDirectory (ProgramFiles3264Folder) and thus can be used to generate stable GUIDs.

You might also read about ComponentGuidGenerationSeed in the docs... but don't use TARGETDIR. :)

[robmen]

Yes, this Discussion forum is a place where you can ask questions about using WiX. There are no guarantees for answers, but like any open community, if you're helpful, other people are usually pretty helpful too. 😄

[robmen]

PS: StackOverflow is a fine place to ask questions, too.

[edgarsad007]

@robmen , I've spend three weeks researching this question but to no avail. I used Wix succfully in version 3 or installing in ProgramFiles folder. I tried many times ask Copilot and Grok 3 but to no avail and it looks like they learned only Wix version 3. I thought installing website in IIS is not unusual. Probably this question should be answered by user of Wix and not developer of Wix. But I would very appreciate if you or any other developer of Wix will answer. What should be instead of "TARGETDIR" in this:

<StandardDirectory Id="TARGETDIR" > <Directory Id="INETPUB" Name="Inetpub"> <Directory Id="WWWROOT" Name="wwwroot"> <Directory Id="INSTALLDIR" Name="testwebsite"/> </Directory> </Directory> </StandardDirectory>
What should be the declaration to install files to "C:\inetput\wwwroot\testwebsite"?

[robmen]

Hmm, inetpub is in a really strange place. Definitely not trivial to install to. I never understood why they put it there. You'll probably need a SetDirectory to change the folder to the SystemVolume. Then maybe use ComponentGenerationSeed if you don't root the folder in a real StandardDirectory.

[h65406]

Thanks Rob for helping out ..
I have a similar problem. I am able to move the payload to the IIS web folder, but the web app is not registered correctly. (shows up but not functional)
I diverted from edgar's approach (after trying for a while ). I explicitly include the files.
I would like the implicit way edgar used to work though .. my explicit approach is too brittle as changes in the payload project would require me to change my installer each time my payload has additions.
I'd like to collaborate with both of you to further the implicit solution ..
(I removed some details for the privacy of my employer)
When the msi finishes ..
..the files are where they need to be

..the app pool I customized shows up - still some discrepancies on whether "No Managed Code" is valid for asp.net8 core web apps (found the app pool creation with property "No Managed Code" looks exactly the same but IIS seems to struggle to accept it .. once I manually change it gets further)

There is a known issue setting it to that value.
Can't set IIS WebAppPool ManagedRuntimeVersion to "No Managed Code" · Issue #5226 · wixtoolset/issues
Working version of support for "No Managed Code" for managedRuntimeVe… by jmcooper8654 · Pull Request #451 · wixtoolset/wix3
Answer is:
don't use PowerShell
and
create a custom action dll and do it there.
That is the only way I could make that work.

I addition make sure that your folders have the correct permissions (IIS USR access at the correct level)
When I manually change the No Managed Code to the other No Managed Code in the app pool, set the folder permissions manually for the install folder and the logs folder .. the app starts and creates logs and runs
My partial product.wxs is

<!-- Directory structure -->
<StandardDirectory Id="TARGETDIR">
	<Directory Id="WWWROOTDIR" Name=".">
		<Directory Id="<somename>" Name="<againsomenametoo>">
			<Directory Id="INSTALLFOLDER" Name="$(var.Console)-v$(var.MajorVersion)"> 
				<Directory Id="LogsFolder" Name="logs" />
				<Directory Id="csDir" Name="cs" />
				<Directory Id="deDir" Name="de" />
				<Directory Id="esDir" Name="es" />
				<Directory Id="frDir" Name="fr" />
				<Directory Id="itDir" Name="it" />
				<Directory Id="jaDir" Name="ja" />
				<Directory Id="koDir" Name="ko" />
				<Directory Id="plDir" Name="pl" />
				<Directory Id="pt_BRDir" Name="pt-BR" />
				<Directory Id="ruDir" Name="ru" />
				<Directory Id="trDir" Name="tr" />
				<Directory Id="zh_HansDir" Name="zh-Hans" />
				<Directory Id="zh_HantDir" Name="zh-Hant" />
				<Directory Id="runtimesDir" Name="runtimes">
					<Directory Id="browserDir" Name="browser">
						<Directory Id="browserLibDir" Name="lib">
							<Directory Id="browserLibNet8Dir" Name="net8.0" />
						</Directory>
					</Directory>
					<Directory Id="linuxDir" Name="linux">
						<Directory Id="linuxLibDir" Name="lib">
							<Directory Id="linuxLibNet8Dir" Name="net8.0" />
						</Directory>
					</Directory>
					<Directory Id="osxDir" Name="osx">
						<Directory Id="osxLibDir" Name="lib">
							<Directory Id="osxLibNet8Dir" Name="net8.0" />
						</Directory>
					</Directory>
					<Directory Id="winDir" Name="win">
						<Directory Id="winLibDir" Name="lib">
							<Directory Id="winLibNet8Dir" Name="net8.0" />
						</Directory>
					</Directory>
				</Directory>
			</Directory>
		</Directory>
	</Directory>
</StandardDirectory>

	<!-- Application Pool - custom app pool creation-->
	<Component Id="AppPoolComponent" Guid="uuidsIlike-56789ABCDEF0" Directory="INSTALLFOLDER">			
		<iis:WebAppPool Id="<mylovelyAppPool>"
		                Name="<samenameagain> [$(var.Console)] v$(var.MajorVersion)"
		                Identity="applicationPoolIdentity"
		                ManagedPipelineMode="integrated"
		                ManagedRuntimeVersion="No Managed Code" />
	</Component>
	
	<!-- Web app component - register with IIS and reference app pool -->		
	<iis:WebSite Id="WebApplicationSiteRef" Description="Default Web Site" Directory="INSTALLFOLDER">
		<iis:WebAddress Id="WebApplicationWebAddr" IP="*" Port="80" />
	</iis:WebSite>
	<Component Id="WebApplicationComponent" Guid="uuidsIlike-123456789ABC" Directory="INSTALLFOLDER" Condition="IISINSTALLED">
		<iis:WebVirtualDir Id="MyWebApp" Alias="[WEBAPP_ALIAS]" Directory="INSTALLFOLDER" WebSite="WebApplicationSiteRef">
			<iis:WebApplication Id="<somename>WebApp" Name="[WEBAPP_ALIAS]" WebAppPool="<MyLovelyappool>"/>
		</iis:WebVirtualDir>
	</Component>
[..]
<DirectoryRef Id="INSTALLFOLDER">
	<Component Id="MainExecutable" Guid="uuidsIlike-75D93621C646">
		<File Id="LicenseFile" Source="license.txt" KeyPath="yes" />				
	</Component>
        <Component Id="WebAppBinaries" Guid="uuidsIlike-ABCDEF012345">
	      <File Id="appsettings_json" Source="..\..\<somePayloadFolder>\bin\Release\net8.0\appsettings.json" />
        	[..]
	      <File Id="System_Spatial_dll" Source="..\..\<somePayloadFolder>\bin\Release\net8.0\System.Spatial.dll" />
	</Component>
</DirectoryRef>
[..]
<!-- DirectoryRef for the logs folder with permissions for the app pool identity -->	
<DirectoryRef Id="LogsFolder">
	<Component Id="LogsFolderPermissions" Guid="uuidsIlike-BCDEF1234567">
		<CreateFolder>
			<util:PermissionEx User="IIS APPPOOL\[<MyLovelyApiAppPool>]"
			                   GenericWrite="yes"
			                   CreateFile="yes"
			                   CreateChild="yes" />
		</CreateFolder>
	</Component>
</DirectoryRef>
<!-- DirectoryRef for the installation folder + set permissions for the app pool identity -->
<DirectoryRef Id="INSTALLFOLDER">
	<Component Id="InstallFolderPermissions" Guid="uuidsIlike-456789ABCDEF">
		<CreateFolder>
			<util:PermissionEx User="IIS APPPOOL\[<MyLovelyApiAppPool>]"
                               GenericRead="yes"
                               GenericExecute="yes" />
		</CreateFolder>
	</Component>
</DirectoryRef>

[.. add any other folder and set permissions, as necessary ..]

<!-- Feature to install the components -->
<Feature Id="MainFeature" Title="<samename> $(var.Console) v$(var.MajorVersion)" Level="1">
	<ComponentRef Id="MainExecutable" />
	<ComponentRef Id="AppPoolComponent" />
	<ComponentRef Id="WebApplicationComponent" />
	<!--<ComponentGroupRef Id="WebAppBinaries"/>  this did not work -->
	<ComponentRef Id="WebAppBinaries" />
	<ComponentRef Id="WebAppBinaries_cs" />
	<ComponentRef Id="WebAppBinaries_de" />
	<ComponentRef Id="WebAppBinaries_es" />
	<ComponentRef Id="WebAppBinaries_fr" />
	<ComponentRef Id="WebAppBinaries_it" />
	<ComponentRef Id="WebAppBinaries_ja" />
	<ComponentRef Id="WebAppBinaries_ko" />
	<ComponentRef Id="WebAppBinaries_pl" />
	<ComponentRef Id="WebAppBinaries_pt_BR" />
	<ComponentRef Id="WebAppBinaries_ru" />
	<ComponentRef Id="WebAppBinaries_tr" />
	<ComponentRef Id="WebAppBinaries_zh_Hans" />
	<ComponentRef Id="WebAppBinaries_zh_Hant" />
	<ComponentRef Id="WebAppBinaries_browser" />
	<ComponentRef Id="WebAppBinaries_linux" />
	<ComponentRef Id="WebAppBinaries_osx" />
	<ComponentRef Id="WebAppBinaries_win" />
	<ComponentRef Id="LogsFolderPermissions" />
	<ComponentRef Id="InstallFolderPermissions" />
</Feature>