This seems like a basic question, but it is one I want to pose to the 
group for feedback. 

I am on a new client side where they have asked me to re-write some FoxPro 
COM components using .NET Web Services.  The COM objects are used by their 
clients to access a sql server data layer.  Each client is free to build 
their own web site as all the sql server data is hosted locally at each 
client site.  

The software application my client sells is a 2 tier, software product 
that is pushed to their clients monthly on a subscription basis.  

So, basically there is a windows client and a limited web client.  All 
client have the windows client, however some have added a web client, 
which is why the foxpro components were written.

I would be re-writing the FoxPro objects as Web Services that each client 
would need to have on their local web servers.  My questions are this:

If each client has to have the web services locally, they would need IIS 
running on their web server, correct? 

They would also need to install the .NET redistributables on the web 
server, correct?

What if the client's web server is not a windows OS.  Can they install 
a .NET web service on a non windows web server? 

    

Greg,

> If each client has to have the web services locally, they would need IIS 
> running on their web server, correct? 

	This is correct.

> They would also need to install the .NET redistributables on the web 
> server, correct?

	Correct again.  All 17.xx MBs of runtimes need to be installed.

> What if the client's web server is not a windows OS.  Can they install 
> a .NET web service on a non windows web server?

	No, currently only IIS supports ASP.NET, and thus only IIS supports
writing a web service in .NET.  There is Microsoft's "Rotor" for FreeBSD
(FreeBSD is the *nix used for Hotmail) but I don't think there's any ASP.NET
support there for it.  There's also the Ximian .NET for Linux, but again
there's no ASP.NET support as no native *n?x web servers supports it.
Apparently there was an announcement at OSCON (O'Reilly Open Source
Convention) that Microsoft will be teaming up with Covalent Technologies to
create a version of Apache that supports IIS - you can read more here:

http://apache.slashdot.org/article.pl?sid=02/07/22/2334239&mode=nested&tid=1
09

	I would imagine that Apache with ASP.NET/.NET would require Rotor or
Ximian's .NET (both available freely distributed; Ximian's is open source)
if you ran it on another non-Win2K-esque OS.

- Chuck

-----Original Message-----
From: greg robinson [mailto:gregarobinson@h...]
Sent: Wednesday, August 07, 2002 10:05 AM
To: ASP+
Subject: [aspx] web service requirements


This seems like a basic question, but it is one I want to pose to the 
group for feedback. 

I am on a new client side where they have asked me to re-write some FoxPro 
COM components using .NET Web Services.  The COM objects are used by their 
clients to access a sql server data layer.  Each client is free to build 
their own web site as all the sql server data is hosted locally at each 
client site.  

The software application my client sells is a 2 tier, software product 
that is pushed to their clients monthly on a subscription basis.  

So, basically there is a windows client and a limited web client.  All 
client have the windows client, however some have added a web client, 
which is why the foxpro components were written.

I would be re-writing the FoxPro objects as Web Services that each client 
would need to have on their local web servers.  My questions are this:

If each client has to have the web services locally, they would need IIS 
running on their web server, correct? 

They would also need to install the .NET redistributables on the web 
server, correct?

What if the client's web server is not a windows OS.  Can they install 
a .NET web service on a non windows web server?