[Mono-bugs] [Bug 520021] New: Page.SetForm() is named Page.RegisterForm() under Mono

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Jul 7 20:32:07 EDT 2009


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


           Summary: Page.SetForm() is named Page.RegisterForm() under Mono
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: CORLIB
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: steve at smartz.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1;
Trident/4.0; GTB6; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR
3.0.04506.30; .NET CLR 3.0.04506.648; InfoPath.2; .NET CLR 3.5.21022; .NET CLR
3.5.30428; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; OfficeLiveConnector.1.3;
OfficeLivePatch.0.0)

In .Net, the class System.Web.UI.Page provides an internal method, named
SetForm.

Under Mono, the method SetForm does not exist.  Instead, there is an internal
method named RegisterForm() which performs the identical task.

We use Reflection to invoke the SetForm() method when building pages
dynamically that host the Telerik RadEditor control.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



One could certainly argue that there is no requirement for internal methods to
be identical.  At the same time, we can't find a suitable solution for
dynamically building pages that host Telerik controls without being able to set
the page's form, among other steps that are necessary to properly construct and
initialize the RadEditor control.

For now, we are checking the runtime environment to see if we are running under
Mono.  If so, we invoke RegisterForm instead of SetForm.

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


More information about the mono-bugs mailing list