[Mono-bugs] [Bug 578880] New: System.Web.Hosting.HostingEnvironment's IsHosted, ApplicationID and SiteName properties not provided for a hosted environment

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=578880

http://bugzilla.novell.com/show_bug.cgi?id=578880#c0


           Summary: System.Web.Hosting.HostingEnvironment's IsHosted,
                    ApplicationID and SiteName properties not provided for
                    a hosted environment
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.6.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: tagdev at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Created an attachment (id=341845)
 --> (http://bugzilla.novell.com/attachment.cgi?id=341845)
The attachment contains a patch with NUnit test code.

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3)
Gecko/20090824 Firefox/3.5.3 GTB6 (.NET CLR 3.5.30729)

When a hosted ASP.NET application domain is created with
System.Web.ApplicationHost.CreateApplicationHost, the static properties of the
System.Web.Hosting.HostingEnvironment class need to be populated for the hosted
environment.  However, Mono 2.6.1 does not initialize the values of the
IsHosted, ApplicationID and SiteName properties and they always seem to contain
their default values.

Reproducible: Always

Steps to Reproduce:
1. Apply the attached patch to
"trunk/mcs/class/System.Web/Test/System.Web.Hosting/HostingEnvironmentTest.cs",
and  
2. Run the new test named "HostedDefaultValues".

Actual Results:  
The test fails.

Expected Results:  
The test should succeed (for example, as it does on .NET 3.5).

The problem also exists on Mono 2.4.x

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.