Example WiX configuration to deploy a simple ASP.NET website

[Bapeappok]

Just starting with WiX (at version 3.8), we're surprised that it doesn't seem at all straightforward to deploy a website with WiX. Not yet concerned about any infrastructure aspects like IIS or custom actions to tailor the setup, or even whether we precompile the site, just would be happy to deploy a trivial website to a folder. But the only file that ever gets deployed is a single dll (whose name appears to be derived from the AssemblyName property configured in the csproj). After some googling, we tried setting Harvest=True on the project reference, and adding \[code\]<EnableProjectHarvesting>True</EnableProjectHarvesting>\[/code\] to the wixproj file. But only that same dll ever gets deployed. (Orca shows it to be the only file in the MSI file table.)Adding the following to the wixproj succeeds in getting Heat, Candle and Light to process a set of files from a hard-coded folder, but does not succeed in deploying anything else: still only the one dll is included in the MSI file table.\[code\]<Target Name="BeforeBuild"> <!-- try hardcoded path --> <HeatDirectory ToolPath="$(WixToolPath)" OutputFile="%(ProjectReference.Filename).wxs" Directory="C:\Dev\2010\HelloWixWebApplication\HelloWixWebApplication" GenerateGuidsNow="true" DirectoryRefId="TARGETDIR" /> <!-- some properties that Candle will use, so we should be able to to tell it to look in this folder for the .wks --> <PropertyGroup> <!--IncludeSearchPaths>.</IncludeSearchPaths --> <CompilerAdditionalOptions>%(ProjectReference.Filename).wxs</CompilerAdditionalOptions> <!--and one for Light: --> <LinkerAdditionalOptions>obj\Debug\%(ProjectReference.Filename).wixobj</LinkerAdditionalOptions> </PropertyGroup></Target>\[/code\]Returning to the main question, and the thing that would really help but we can't seem to find: an actual example of deploying a simple asp.net website using WiX. Anyone? TIA.