[Mono-bugs] [Bug 664809] New: Incomplete System.Web implementation prevents ASP.NET MVC 3 from view resolution

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sun Jan 16 06:37:56 EST 2011



           Summary: Incomplete System.Web implementation prevents ASP.NET
                    MVC 3 from view resolution
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.8.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: piotr.walat at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10

It seems that ASP.NET MVC 3 uses BuildManager.GetObjectFactory(virtualPath,
false) != null condition to check if given view file exists. 
Mono 2.8 implementation of BuildManager.GetObjectFactory() (System.Web 4.0)
method looks like this (method marked as TODO): 

[MonoTODO("A no-op until we use IWebObjectFactory internally. Always returns
public static IWebObjectFactory GetObjectFactory(string virtualPath, bool
    return null; 

This causes view resolution to fail because FileExist check will always yield a
negative result.

Reproducible: Always

Steps to Reproduce:
1. Create an empty ASP.NET MVC 3 application
2. Return ViewResult in default controller's (Home) Index action
3. Create Index view (using either WebForms or Razor view engine)
4. Run the application and try to navigate to /Home/Index
Actual Results:  
Index view cannot be found even though residing in proper location (case taken
into account).

Expected Results:  
Index view should be displayed instead of exception/error message

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

More information about the mono-bugs mailing list