I would like the ability to decide whether to use an
existing
Application pool when a web service is installed, rather
than
creating a new one. The name of the Application pool
could be
input from a Custom Action which takes values from the
command
line at install time.
If I did want new application pool to be created, I want to
be able to
specify the identity it runs under and the username and
passeord associated
with it, again via Paraterised values through a Custom
Action, not by
hardcoding values into my WiX sourcefile. Being able to
specify the
name of the pool in this way would also be good.
I think allowing for the 'ConfigureIIS' custom action to be
overloaded
with parameterised values might achieve the above - at
the moment this generates
duplicate file exceptions.
At the moment I am faced with the propspect of using
IIS admin scripts via
Custom Actions to achieve the above.
I would like the ability to decide whether to use an existing Application pool when a web service is installed, rather than creating a new one. The name of the Application pool could be input from a Custom Action which takes values from the command line at install time.
If I did want new application pool to be created, I want to be able to specify the identity it runs under and the username and passeord associated with it, again via Paraterised values through a Custom Action, not by hardcoding values into my WiX sourcefile. Being able to specify the name of the pool in this way would also be good.
I think allowing for the 'ConfigureIIS' custom action to be overloaded with parameterised values might achieve the above - at the moment this generates duplicate file exceptions.
At the moment I am faced with the propspect of using IIS admin scripts via Custom Actions to achieve the above.
bq. Originally opened by @turnera1@ from "http://sourceforge.net/p/wix/feature-requests/79/":http://sourceforge.net/p/wix/feature-requests/79/