Hello WiX Community,
I have been browsing for the way to register ASP.NET 2.0 script maps for
a site through this archive, and found an option to call the
aspnet_regiis -s in the following custom action:
<CustomAction Id="SetAspNet20" Directory="TARGETDIR"
ExeCommand=""[NETFRAMEWORK20INSTALLROOTDIR]aspnet_regiis.exe"
-s W3SVC/[SITEID]/ROOT" Return="check" />
It is scheduled after InstallFinalize like this:
<InstallExecuteSequence>
<Custom Action="SetAspNet20" After="InstallFinalize">condition
here</Custom>
</InstallExecuteSequence>
However, if the site is also created in this very installation, the
action somehow crashes ASP.NET. After the installation the call to any
site gives "Page not found" and can be fixed only by aspnet_regiis -u
and then aspnet_regiis -i. If the site exists before the installation,
everything is fine.
This makes me think that there is a certain rule I violate or a bug in
IIS extension (e.g. transaction is not closed / changes are not saved,
when I set script maps).
Does any of you know what might be wrong here? You suggestion is highly
appreciated.
I'm attaching the sample project for more direct example.
Thank you!
-- Yan
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
