[Mono-bugs] [Bug 535655] New: ProfileCommon class fails to generate when Profile Properties

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Aug 31 12:02:21 EDT 2009


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


           Summary: ProfileCommon class fails to generate when Profile
                    Properties
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: Other
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: william.leader at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.2)
Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)

When using ASP Profiles in an ASP website it is possible to define groups for
the profile properties (See:
http://msdn.microsoft.com/en-us/library/d8b58y5d.aspx). Using the MySQL
Membership, Role, and Profile Providers included in the MySQL Connector/.Net
(http://dev.mysql.com/downloads/connector/net/5.2.html) it is possible to
create an ASP website that stores its login and profile information in a MySQL
database.

Using an ASP website's web.config file it is possible to specify profile
properties. Once this is done a class known as ProfileCommon is generated that
exposes these properties to the application code. As long as the properties are
not in a group, the website will run as expected in a Mono environment such as
XSP. However if the profile properties definition in the web.config utilizes
groups to organize the properties, a Microsoft hosting environment will produce
the ProfileCommon class, but a Mono hosting environment (XSP) will not
correctly generate the ProfileCommon class. This prevents any pages that use
ProfileCommon from running as expected.

There is a discussion of this behavior at
http://www.nabble.com/ProfileCommon-not-automatically-generated-under-XSP-td25220499.html

Reproducible: Always

Steps to Reproduce:
1. Create a web application that uses the MySQL Profile Provier.
2. Specifiy Profile Properties that use Groups.
3. Create code for the web application that uses the ProfileCommon class.
4. Load a page that utilizes the ProfileCommon class when hosted in XSP.
Actual Results:  
An error page will be displayed:

Compiler Error Message: CS0246: The type or namespace name `ProfileCommon'
could not be found. Are you missing a using directive or an assembly reference?

Expected Results:  
XSP should generate the ProfileCommon object and compile it allowing the page
to run without error.

Behavior has been observered in the XSP server that ships with Mono 2.2 and
2.4.3.2

A simple work around is to not use the group feature to group profile
properties.

-- 
Configure bugmail: http://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