We are trying to standardize on a solid, open, secure Web Server
architecture. We are running Apache 2 on Windows 2003 Server. For
static HTML, JSP and ColdFusion apps, this is running perfectly, but now
we need to be able to run ASP .NET applications. I have read about the
"mod_mono" module for Apache that allows .NET applications to run on
Apache, but this seems to only work with Apache on Linux, not Windows.
Anyone have success with getting ASP .NET apps to run under Apache on
Windows?

And what's wrong with IIS6? As long as you keep it patched (just like you
have to with all the vaunted "bug-free" and "perfect" open source apps) it
works fine.

Mono is still to immature (IMO) to trust it with a real production website.

You can of course write your own. It's actually not that difficult with .NET
as long as you don't need it to scale much.

--
____________________
Klaus H. Probst, MVP
http://www.vbbox.com/

"michael [multnomah]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We are trying to standardize on a solid, open, secure Web Server
> architecture. We are running Apache 2 on Windows 2003 Server. For
> static HTML, JSP and ColdFusion apps, this is running perfectly, but now
> we need to be able to run ASP .NET applications. I have read about the
> "mod_mono" module for Apache that allows .NET applications to run on
> Apache, but this seems to only work with Apache on Linux, not Windows.
> Anyone have success with getting ASP .NET apps to run under Apache on
> Windows?

Klaus H. Probst wrote:

> And what's wrong with IIS6? As long as you keep it patched (just like you
> have to with all the vaunted "bug-free" and "perfect" open source apps) it
> works fine.
>

I understand that with patching, both IIS6 and Apache 2 can be solid,
secure HTTP servers, but the issue with our organization is that we are
moving in the direction of open source systems, period. Once we get
Apache, Tomcat and .NET running on Windows 2003, that entire web
environment can be ported to Linux with little or no changes at all [if
and when that time comes]. That means that our developers can develop
with open source tools, the apps can run in an open source environment,
and the only proprietary system is our server OS. Don't get me wrong, I
think Windows 2003 is an excellent server OS and it is very easy to
administer. But being realistic with budget cuts and the general trend
towards open systems, it is only a matter of time [within 2 years]
before we take out Windows and put in Linux for the OS.

I thought IIS + Apache can't start simultaneously??

If I have the IIS + ASP.NET running as a Service, the Apache 2.0 won't run,
because a Server Service is already running and I have to close the IIS
Service.