[Mono-list] Custom memberhsip blues => could not find type: MySqlMembershipProvider

steve at enerds.ca steve at enerds.ca
Mon Mar 19 02:11:59 EDT 2007



   Mike,

     Thanks for that "one last thought" - that solved it (and saved my  
sanity).  I was using the RPM's for RHEL / CentOS  (v1.2.3.1-0).  Just  
grabbing & compiling mono, mod_mono, xsp from the trunk in the svn  
repo fixed the issue.

   The app started working as expected - with my custom  
MySQLMembershipProvider located in the App_Code/ folder.

   Cheers!
~Stephen

   ----- Message from mmorano at mikeandwan.us ---------
    Date: Sun, 18 Mar 2007 22:19:51 -0400
    From: Mike Morano <mmorano at mikeandwan.us>
Reply-To: Mike Morano <mmorano at mikeandwan.us>
Subject: Re: [Mono-list] Custom memberhsip blues => could not find  
type: MySqlMembershipProvider
      To: steve at enerds.ca

> Hmm.. one last thought.  There were some bugs fixed the past week or two
> that address how to find references to classes that are in App_Code.
> Are you using mono from svn?  If not, what version?
>
> Additionally, as I have been testing my site, I just point xsp2 at the
> root of the site.  I do not compile anything, including the App_Code,
> and just let the framework manage that.  When I run it this way, it is
> able to resolve the class appropriately.
>
> Hope that helps,
> Mike
>
>
> On Sun, 2007-03-18 at 20:07 -0600, steve at enerds.ca wrote:
>> Hi Mike,
>>
>>    Thanks for the reply. All my other DB code seems to be working fine
>> - it's v5.05.
>>
>> Before posting to the list I just created a simple "MyProvider" that
>> inherited from MembershipProvider, implemented all the required
>> methods for the interface, tossed it into App_Code  (and tried manual
>> compile to the bin/ directory).  This way, I could rule out MySQL as
>> being the source of the errors.
>>
>> I keep getting the "could not find type" error that I posted before.
>> Very interesting.
>>
>> ~Stephen
>>
>> ----- Message from mmorano at mikeandwan.us ---------
>>      Date: Sun, 18 Mar 2007 18:33:21 -0400
>>      From: Mike Morano <mmorano at mikeandwan.us>
>> Reply-To: Mike Morano <mmorano at mikeandwan.us>
>> Subject: Re: [Mono-list] Custom memberhsip blues => could not find
>> type: MySqlMembershipProvider
>>        To: Stephen March <steve at enerds.ca>
>>        Cc: Mono-list at lists.ximian.com
>>
>>
>> > Hello,
>> >
>> > I'm currently able to use my custom membership provider, and similar
>> to
>> > your's, am connecting to mysql.  I'm running mono from svn and xsp2
>> on
>> > linux.
>> >
>> > Additionally, I am using the "official" mysql drivers (v5.0.5), and
>> had
>> > a couple different issues with them, so am running a modified
>> version of
>> > the original source with a few hacks in place to avoid places where
>> it
>> > was dying on me.  Perhaps it is a problem with this rather than the
>> > provider itself?  Is any of your other db code working?
>> >
>> >
>> > -Mike
>> >
>> >
>> > On Sun, 2007-03-18 at 16:08 -0600, Stephen March wrote:
>> >> Hey folks,
>> >>
>> >>
>> >>
>> >>         I’m trying to create a custom membership provider for use
>> on
>> >> Linux. I keep on getting the error “could not find type:
>> >> MySqlMembershipProvider”.  I’ve tried wrapping it in a different
>> >> namespace, and also manually compiling it and placing it into the
>> bin
>> >> directory. My web.config looks like this:
>> >>
>> >>
>> >>
>> >>             <membership defaultProvider="MyProvider"
>> >> userIsOnlineTimeWindow="15">
>> >>
>> >>                   <providers>
>> >>
>> >>                         <clear/>
>> >>
>> >>                         <add name="MyProvider"
>> >>
>> >> type="MySqlMembershipProvider"
>> >>
>> >> connectionStringName="StrConn"
>> >>
>> >> applicationName="Mono"
>> >>
>> >> enablePasswordRetrieval="false"
>> >>
>> >> enablePasswordReset="true"
>> >>
>> >> requiresQuestionAndAnswer="false"
>> >>
>> >> requiresUniqueEmail="true"
>> >>
>> >> passwordFormat="Hashed"/>
>> >>
>> >>                   </providers>
>> >>
>> >>                </membership>
>> >>
>> >>
>> >>
>> >> Currently my provider code is located in the App_Code directory
>> (this
>> >> works fine on Windows, .NET 2.0 through IIS)
>> >>
>> >>
>> >>
>> >> On my Linux setup the connection string is to a local MySQL
>> database
>> >> with the MySql client connector. I have several object data sources
>> >> that pull off of my custom business classes, making use of
>> generics,
>> >> etc. So I know I’m on ASP.NET 2.0, things appear to be configured
>> >> correctly .. it just seems that the web.config is processed before
>> my
>> >> custom provider is compiled and included.
>> >>
>> >> erver2)
>> >>
>> >>
>> >>
>> >> Any thoughts?
>> >>
>> >> Best regards,
>> >>
>> >>
>> >> ~Stephen March
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> Mono-list maillist  -  Mono-list at lists.ximian.com
>> >> http://lists.ximian.com/mailman/listinfo/mono-list[1]
>> >
>>
>>
>> ----- End message from mmorano at mikeandwan.us -----
>>
>>
>

----- End message from mmorano at mikeandwan.us -----


Links:
------
[1] http://lists.ximian.com/mailman/listinfo/mono-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20070319/7cc07165/attachment-0001.html 


More information about the Mono-list mailing list