January 2007 Entries

DotNetNuke changes in Web.Config from 4.0.3 to 4.4

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.SqlMem... and profile providers sections ......

Parser Error Message: Access to the path is denied. caused by SourceSafe merge.

I've used Visual SourceSafe Merge method to merge changes from different brunches of the ASP.NET site project. VSS created merged file, as well as renamed original file with .org extension. (By the way, it is not widely known, that VSS creates a backup copy of the original file filename.ext.ORG, that can be used to restore file, if merge unsucceded by some reason). However when I started to run the ASP.NET application in IIS, it caused "Access to the path" errors, e.g. Parser Error Message: Access ......

DotNetNuke.Services.Upgrade.ExecuteScripts method

DotNetNuke function Upgrade.ExecuteScripts(ByVal strProviderPath As String)actually doesn't use strProviderPath, but always uses ApplicationMapPath & "\Install\Scripts\" folder. It reads all files in the folder and deletes them after execution. It is also triggered only by InstallDNN.The behavior is different to install\modules folder, where modules are installed also during UpgradeDNN. The issue reported here(in comments). I've also asked a question in DNN Forums "Is "install\scripts" folder ......