We're targeting .NET 1.1 and eventually 2.0. I've run mod_aspdotnet with
2.0 and have had encouraging results. We put the .NET 1.1 framework
install into our kits before installing our application software so it
is a very smooth process. We're also using VS.NET 2003 for our
development. I don't see anything else required and would highly
recommend using .NET 1.1 if possible. It fixes quite a bit of things and
we would not consider going into production with .NET 1.0. I haven't
tried installing with .NET 1.0 so I don't have any info there. I've also
done performance testing versus IIS and things look very good with
mod_aspdotnet. 

Our application got the go ahead to convert to .NET 6 months ago so we
have a small percentage of functionality to get our feet wet. Our next
release will be substantial .NET functionality and may well be .NET 2.0
in the spring 2006. Our security requirements at our customer site don't
allow using IIS so we are depending on mod_aspdotnet to work for us and
I'm very happy with what I've seen so far. We'll have quite a few users
using it by the end of the year. 

Heino

-----Original Message-----
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 01, 2005 12:55 PM
To: cli-users@httpd.apache.org
Cc: cli-users@httpd.apache.org
Subject: RE: [cli-users] System.OutOfMemoryException

At 11:47 AM 9/1/2005, Pull, Heino wrote:
>This is great news. We are going into production with mod_aspdotnet and
>I have to use the MTA/STA fix to have a stable application. Otherswise
>our application leaks like crazy and brings down the server. 

Of course!  That leak :)

>Our Air Force customer knows about this module and will be likely to
>download the latest release version (2.0.0.0) so we have to deliver
with
>our kits the release version which has been compiled with the fix. By
>the way, I have been successfully installing mod_aspdotnet on Windows
>2000 server without IIS installed. We are going through formal tests
>targeting Windows 2000 server and all seems to be well.

Glad to hear - is there anything we need to change in the installer
or otherwise to make mod_aspdotnet behave if IIS has never been
installed?  Was this with the .NET 1.0 or 1.1?  I'm thinking if you
had no extra steps - perhaps they got this right after 1.0.

Bill 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to