After some testing I have discovered that it is the use of Groups in the profile properties in the web.config that causes the problem. If I modify my web.config properites section as follows, then the code works fine in XSP in Mono.
<properties> <add name="GamesJoined" type="Int32" serializeAs ="String" defaultValue="0"/> </properties> Which means that as a work around I can just not use property groups, which is less than ideal. I have found that removing the groups from the profile properties section corrects the problem on both mono 2.2 and 2.4.2.3, so now I need to determine if this is caused by the profile provider or some code inside Mono itself. -Will On Mon, Aug 31, 2009 at 11:14 AM, william leader <[email protected]>wrote: > Hello, > > What I had installed is mono 2.2, and the error page reports: *Version > information: * Mono Version: 2.0.50727.1433; ASP.NET > <http://asp.net/>Version: 2.0.50727.1433 > > Just to be sure I've tried running under mono 2.4.2.3, and I get the same > error message, except now the error page no longer shows the line numbers > which is less helpful. > > I'm not convinced this is a bug since as Marek points out This feature has > been around for three years. I'm more inclined to believe I'm doing > something wrong like I am missing a parameter or setting somewhere. > > -Will > > On Mon, Aug 31, 2009 at 10:26 AM, Marek Habersack <[email protected] > > wrote: > >> wleader wrote: >> >>> Hello, >>> >> What is the Mono version you're using? ProfileCommon has been supported in >> Mono since 2006. >> If you're using the latest mono and still see the issue, then this is a >> bug - please file a bug (http://mono-project.com/Bugs) with a >> self-contained test case attached. If you're using some old version of Mono, >> please upgrade. >> >> marek >> >> >> I am building my ASP.Net 2.0 application using Visual Studio as my IDE. >>> As I >>> make changes I like to test with both the development server included >>> with >>> Visual Studio, and also with XSP running inside the mono runtime in >>> Windows. >>> My presumption is that testing this way I can be sure to write code that >>> works on .Net hosts and Mono hosts. >>> >>> Currently I am working on adding a feature that uses Profiles, and I have >>> things working using the MySQL Profile Provider under the Visual Studio >>> web >>> server. >>> So far I have added the following to my web.config >>> >>> <profile defaultProvider="MySQLProfileProvider"> >>> <providers> >>> <remove name="MySQLProfileProvider"/> >>> <add name="MySQLProfileProvider" >>> type="MySql.Web.Profile.MySQLProfileProvider, >>> MySql.Web,Version=5.2.5.0,Culture=neutral, >>> PublicKeyToken=C5687FC88969C44D" >>> connectionStringName="LocalMySqlServer" >>> applicationName="/" /> >>> </providers> >>> <properties> >>> <group name="GameStats"> >>> <add name="GamesJoined" type="Int32" serializeAs ="String" >>> defaultValue="0"/> >>> </group> >>> </properties> </profile> >>> >>> Once that was done inside visual studio, I was able to start using the >>> ProfileCommon object which appears to be automatically generated by the >>> compiler. In the code I can then do the following: >>> >>> ProfileCommon profile = (ProfileCommon.Create("ValidUsername") as >>> ProfileCommon); >>> LabelUsername.Text = profile.UserName; >>> TextBoxGamesJoined.Text = profile.GameStats.GamesJoined.ToString(); >>> >>> This works great under the visual studio developement server, but when I >>> attempt to load a page with this code on XSP I get the error message: >>> >>> Compiler Error Message: CS0246: The type or namespace name >>> `ProfileCommon' >>> could not be found. Are you missing a using directive or an assembly >>> reference? >>> Does anyone have advice about what I can do to get profile code that >>> works >>> on both .Net and Mono hosts? >>> >>> Thanks, >>> -William Leader >>> >> >> >
_______________________________________________ Mono-aspnet-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
