Hi Kevin,

Here is a reference to another site that has a white paper using Apache.

http://www.covalent.net/products/rotate.php?page=93


>Up until recently, I had believed that a .NET application [and specifically one using Web Services] could only run on IIS, and that it would not run on Apache.
>
>However, a potential client just told us that there had been changes made [either directly or indirectly] to Apache so that a Web Service written in .NET could run on Apache.
>
>Is this true? If so, I have some questions...
>
>1) Would we need to maintain two sets of Web Services, one for IIS and one for Apache?
>
>2) Our Web Server/service does some 'remoting' with the middle tier [the middle tier resides on another server]. So we have a remoting 'client' on the Web Server. Would this run 'as is', or would modifications be required?
>
>3) I have a reference to a Web Site from Ximian, who has some projected called 'Mono', which creates an open source implementation of the .NET Development Framework. In reading through the web site [http://www.go-mono.com/], I do have to wonder if the level of integration is as tight as the 'Microsoft' environment. [Might be a naive or silly question to ask, but I figured I'd ask].
>
>Bottom line is that we have a potential client who is screaming loudly about the use of IIS, and feels that Apache will do the trick. Basically, they're saying that it's not a question of whether IIS will get 'hacked'...it will be hacked frequently So if anyone also has something that we can respond with, that would be great.
>
>Thanks,
>Kevin