Geeks With Blogs

News My Blog has been MOVED to https://mfreidge.wordpress.com
Michael Freidgeim's OLD Blog My Blog has been MOVED to https://mfreidge.wordpress.com

I moved from DNN 4.0.3 to DNN 4.4 and noticed that there are significant web.config changes (actually as a part of 4.3 Membership Services Provider Abstraction ).

However I didn't find any clear documentation about Web.Config changes.
From my understanding the folowing changes happened:
1. Microsoft ASP.NET  membership  defaultProvider changed from "DNNSQLMembershipProvider" to standard MS AspNetSqlMembershipProvider -System.Web.Security.SqlMembershipProvider.
2.roleManager and profile providers sections were deleted from system.web section of web.config.
3. New sections "members","roles","profiles" were added to  "dotnetnuke" sectionGroup

 

Posted on Monday, January 15, 2007 12:26 PM DotNetNuke | Back to top


Comments on this post: DotNetNuke changes in Web.Config from 4.0.3 to 4.4

# re: DotNetNuke changes in Web.Config from 4.0.3 to 4.4
Requesting Gravatar...
Can you be more clear on what you are trying to understand?

The reason the abstraction was done was because DotNetNuke didn't implement the providers as well as it could have been done originally. To best summarize what was done:

AspNet providers were collected into a single project. DotNetNuke uses the original (renamed) providers for Membership and for Roles. The default concrete profile provider shipping with DotNetNuke was designed to work w/ the new registration builder. (using profile properties).
Left by Chris Paterra on Jan 15, 2007 12:40 PM

# re: DotNetNuke changes in Web.Config from 4.0.3 to 4.4
Requesting Gravatar...
Chris,
I have automated Web Setup project to install new version of my (DNN base) application. It has own web/config settings additionally to DNN settings.
When I updating to the new version, I need to make a decision, should I replace the whole existing web.config with the new one(as DNN does) and then restore customer settings to their preferred values OR update existing web.config with the changes for a new version.

This is why documentation about Web.Config changes is important for me.
Left by Michael Freidgeim on Jan 15, 2007 1:00 PM

Your comment:
 (will show your gravatar)


Copyright © Michael Freidgeim | Powered by: GeeksWithBlogs.net