Thank you for this article, which is much needed. Very useful, but I have a number of minor criticisms and suggestions:
p 3. Para 10. “If you want a website and not just a virtual directory,…” Please explain further. Does this apply only to Windows 2003 where IIS6 can host multiple websites? Or can it also apply to Windows XP? And I feel “make the changes required in the Dotnetnuke database (PortalAlias table)” needs much more explanation.
P4 para 1. “If you want the complete sources,…” I may be wrong but I think if you only used VWD as many new users will, and not Visual Studio 2005, then the source version of DNN 4.x isn’t going to much use to you since you can't compile it? Perhaps someone can confirm?
P5 para 3. “you will have to open and edit the Dotnetnuke.sln…” Again this only applies to Visual Studio users. VWD users do not use .sln files.
P5 para 6 “…the DotNetNuke_4_3_5 starterkit.vsi. More on this later…” I can’t find any later reference. Another article?
P7 para d “..change any of the sections that create cookies…” That sounds a useful tip. I don’t remember seeing that anywhere else!
P7 para e “..in this case ‘dnn_fingerfuel’…” but your example shows ObjectQualifier=”finger_” which is confusing
P10 para g. You don’t explain that application pools apply only to Windows 2003 and IIS6, so XP users are going to hunt around in vain! Incidentally, the problem you mention in para g is probably that if you run both .NET 1 and .NET 2 websites on the same server, using the same application pool, you hit strange problems! The solution is to create an application pool and call it something like “Pool for .NET 2” and make sure all .Net 2 websites use it.
|