I guess I don't fully understand what IIS does/is! I can appreciate the need
for the host/server to be running IIS but it 'appears' restrictive for your
clients to need to do the same. I have created two web projects, both with
host and client apps. One is a web service and the other using .NET
Remoting.
When I try to install the client app. (web app) of either, it attempts to
install to the (localhost), whereby if the machine is not running or similar
then it fails to install. I cannot change the destination folder because it
automatically tries to create a 'virtual directory' in the localhost folder.
So my question is.....Is this correct? If so, is there a way to
automatically install (or attempt to) IIS through running some sort of
script during installation? I know VS.Net setup projects allow you to check
'Launch Conditions' and run 'Custom Actions'. Has anyone done this or got
any info.?
Cheers for now.
Phil
for the host/server to be running IIS but it 'appears' restrictive for your
clients to need to do the same. I have created two web projects, both with
host and client apps. One is a web service and the other using .NET
Remoting.
When I try to install the client app. (web app) of either, it attempts to
install to the (localhost), whereby if the machine is not running or similar
then it fails to install. I cannot change the destination folder because it
automatically tries to create a 'virtual directory' in the localhost folder.
So my question is.....Is this correct? If so, is there a way to
automatically install (or attempt to) IIS through running some sort of
script during installation? I know VS.Net setup projects allow you to check
'Launch Conditions' and run 'Custom Actions'. Has anyone done this or got
any info.?
Cheers for now.
Phil
Comment