This is the first appearance of the term “sueet” in the DBVT lexicon. Think “Sweet” with a “u.” I’ll fill you in on all of that over time, but for now please bear with me and regard “Sueeties” as equivalent to CS Nuglets.
My first BlogEngine.NET Sueetie has to do with upgrading membership from BE 1.3 to BE 1.4. I wanted to upgrade my laptop copy of BE.NET before taking it to Beach Week tomorrow and in the process encountered some membership provider issues. I’m using the ASPNET Membership provider with BE.NET so I can integrate membership with my Photo Gallery application, Gallery Server Pro. Both share the same membership, and I intend to use that same shared ASPNET Membership model as I add other Open Source .NET applications to DBVT.COM and elsewhere.
There have been a number of posts to the BE.NET Discussion Board this week about problems logging in after upgrading to 1.4. This is because the BE.NET Provider Model has been substantially updated. Al Nyveldt addresses some of the web.config provider setup changes in his upgrade guide. Al mentions that the MSSQLBlogProvider is gone, replaced with DbBlogProvider. I set the default Membership and Roles provider from the default XML Providers to the DB Providers and was encountering a number of issues like bad “be_user” table object, no column named “password” and other errors having to do with the ASPNET_ Membership tables.
Then I specified the SqlMembership and SqlRole Providers for my membership and role management defaults and everything is, um, SUEET now. This is probably common knowledge to those of you with ASP.NET Membership experience, but I haven’t had a lot of opportunity to work with it until recently. The final step was assigning the same applicationName property as my Photo Gallery ASP.NET Membership providers and we’re back in the business of sharing membership, but now with BE.NET 1.4, baby!