By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,806 Members | 1,841 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,806 IT Pros & Developers. It's quick & easy.

Does the client have to be running IIS??

P: n/a
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
Jul 23 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a

"Phil" <Ph**@nospam.com> wrote in message
news:cr**********@hercules.btinternet.com...
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


You'll probably get a better answer to this in an IIS or VS.NET group, not
an MSSQL group.

Simon
Jul 23 '05 #2

P: n/a
You should only need to create a web application on a server. Clients
will connect through a web browser.

Jul 23 '05 #3

P: n/a
"Phil" <Ph**@nospam.com> wrote in message
news:cr**********@hercules.btinternet.com...
I guess I don't fully understand what IIS does/is!


Yep.
You just put IIS on the web server.

When you're doing web development you might also want your development
machine to act as a web server.
That's one of them exceptions proves the rule things.

GROSS OVERSIMPLIFICATION.
An ASP or ASPX web app runs on both the client AND on the web server.
With scripts which are marked to run on server, it's IIS which does that
running.
Plus some other stuff.

I think maybe you want to browse on over to msdn and look up IIS, see what
it does before you try writing, let alone distributing any apps.

--
Regards,
Andy O'Neill

Jul 23 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.