We have installed and upgraded quite a few sites to the latest DNN version, 4.5.3, that came out last week and most went seamlessly. However, we have found one issue that has raised it's ugly head quite a few times. After upgrading, if you clicked on "Register" you would be redirected to an admin skinned page with no account fields/content. Looking at the url you can see "/ctl/returnurl". Since the site(s) uses a custom page using a 3rd party module for registration for the account info, it is specified in Admin > Site Settings > Advanced Settings > Page Management > User Page.

Here is the error message:

System.Web.HttpException: Could not load type ''. ---> System.ArgumentException: String cannot have zero length. at System.Reflection.Assembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase) at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) --- End of inner exception stack trace --- at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors)

Luckily we found a post on the DNN Forums concerning the quick fix...

4.5.3 New user registration not working if specific page defined

In the above post someone else was having a similar issue. It looks like there was a bug reported as well:

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=5746

While there could definitely been a longer or better description of the problem, it was quickly closed with "unable to reproduce in 4.5.3" the next day without any followup. Luckily the thread on the forums gained the interest of other having the issue and vitkoz was kind enough to run it through debugging to find the issue and hence the issue has been reopened in the DNN issue tracker.

Here is his fix:

"In the file admin/skins/user.ascx.vb, line 142 needs to be changed:

 FROM THIS:

Response.Redirect(NavigateURL(PortalSettings.UserTabId,"returnurl=" & ReturnUrl), True)

TO THIS:

Response.Redirect(NavigateURL(PortalSettings.UserTabId, "Register","returnurl=" & ReturnUrl), True)

You can simply go to that file, make that change, and IIS will recompile it on the next run." - vitkoz

After a brief debut of DNN 4.5.2 on Tuesday, DNN 4.5.3 was released today. Here is a list of changes in 4.5.2:

	Component	Issue Type	Issue ID	Summary	Resource	Status
(4.5.2) Stabilization Release	Admin / Host Functions	Bug	DNN-5516	Exclude .dnn.config file from Module Packaging		Checked-In
	Admin / Host Functions	Bug	DNN-5452	AddRoleGroup does not return new RoleGroupID		Checked-In
	Admin / Host Functions	Bug	DNN-5529	Adding a Page in 4.5.1 Puts the Page Name in the other fields on edit		Checked-In
	Admin / Host Functions	Bug	DNN-5703	URL Control and postback? when?		Checked-In
	Admin / Host Functions	Bug	DNN-5546	Import Portal Template fails due to unknown attributes	>Shaun Walker	Checked-In
	Admin / Host Functions	Enhancement	DNN-5724	Date/Time Edit Controls		Checked-In
	Admin / Host Functions	Enhancement	DNN-5649	Block website access based on defined criteria	>Joe Brinkman	Checked-In
	Admin / Host Functions	Enhancement	DNN-1901	Please expose CDO configuration field "smtpserverport" in Host Settings tab.		Checked-In
	Admin / Host Functions	New Feature	DNN-5536	Log application shutdown reason		Checked-In
	Admin / Host Functions	Task	DNN-4371	Generated html code needs tidying		Checked-In
	General	Bug	DNN-5691	GeoIP Detection		Checked-In
	General	Enhancement	DNN-5725	Add TokenReplace support for Custom Profile Properties		Checked-In
	Installation / Upgrade	Bug	DNN-5720	Versioning in Module Definitions doesn't work		Checked-In
	Installation / Upgrade	Bug	DNN-5690	Exception during installation of 4.x WSP modules	>Shaun Walker	Checked-In
	Installation / Upgrade	Bug	DNN-5483	Edit Module Definition / Update erases the state of DNN Interfaces		Checked-In
	Localization / ML	Bug	DNN-5526	Resource Verifier does not catch all resource files		Checked-In
	Localization / ML	Bug	DNN-2612	XML Error in Resource Verifier		Reopened
	Security	Bug	DNN-5510	Permission Grid - Username Edit - Enables All Users Edit		Checked-In

I am not sure what was changed in DNN 4.5.3 except for the following task in Gemini:

	Component	Issue Type	Issue ID	Summary	Resource	Status
(4.5.3) Stabalization Release	Admin / Host Functions	Bug	DNN-5736	Admin notification of User/Vendor (un)registration contains empty fields		Checked-In

Scott Schecter made a post on his blog about how to disable new search features in DNN 4.5.2. I have not checked to see if these changes still apply to DNN 4.5.3.

Anyone know what else prompted the new release today?

UPDATE 6-1-2007:

Joe Brinkman of the core team commented that it was security related and provided a URL to Sebastian Leupold's post concerning the upgrade. Here is the list:

We have immediate openings for DotNetNuke Module Developers.

1. VB.Net or C#
2. SQL Server
3. Visual Studio 2005
4. Code Generation Techniques
5. DotNetNuke

1. EntitySpaces
2. Gemini
3. Subversion
4. CruiseControl.Net
5. VB.Net AND C# (Ability to read and code in both)

1. You must love code.

         If you didn’t love it, you wouldn’t be doing it, right?

1. The weak shall not apply.

Request for more information and resumes can be submitted to careers (at) venexus (dot) com. No recruiters please!

If you didn't catch it, DotNetNuke announced the first officially sponsored DotNetNuke conference in Las Vegas November 5-8, 2007. Last year was the first time I had been to Vegas, when we went to a modular software development conference last September. It was fun meeting some of the guys in the DNN community and I look forward to meeting them and others again this year. According to Joe Brinkman's blog, DotNetNuke is actively seeking speakers to submit session proposals and selected speakers will receive "3 nights of lodging at the Mandalay Bay Casino and Hotel". While I probably will not be giving a speech, Michael, Scott and I have already marked our calendars, and we may have to twist the arm of a couple more staff to go with us, depending on development schedules. Sounds like fun, see ya there!

Continuous integration is a software development term describing the process that completely rebuilds and tests applications frequently. We recently implemented a continuous integration environment to “publish” our DotNetNuke modules to our development/staging DotNetNuke sites.

The main advantages of a continuous integration environment are:

• Issues are detected and fixed continuously!
• Enhancements and new features are published continuously!
• You are warned about problematic code before it is published.
• Immediate unit testing of all changes.
• Constant availability of a "current" build for testing, demos, or releases.
• Bragging rights for developers who have the least number of broken builds.
• Huge conservation of time when considering the normal administrative process of Build > Package > install in DNN > Test.
• Did I mention this is continuous?

How Our CI and DNN Environment Works

Below is a picture to show you the basics of how our continuous integration environment works.

Disclaimer:

1. If you are running Visual Studio 2005 Web Developer Express, our setup will not work for you. You can stop reading here, or upgrade, unless you are just curious, then read on…
2. There have been long discussion on Web Site Projects (WSP) versus Web Application Projects (WAP) and this post is not one to argue about which is better, rather than to say this is what we do, and the basics of how it works.
3. You are free to comment and collaborate with others on this post. Feel free to even argue about WAP versus WEP, or that you may know of a way to integrate CI with DNN and WSP, we really do not care. However, we do not have time to walk you through setting any of this up, so please do not ask…unless you are interested in one of our DNN support packages, then by all means we can help ;-)
    

Basics of the process:

1. A developer “commits” the DNN module code to Subversion.
2. The commit triggers CruiseControl.Net to “build” the DNN module using a “Trigger” for the project.
3. CruiseControl.Net can be configured to unit test the module before publishing.
4. An “ExecutableTask” is used with our custom assembly publisher application to send the .DLL file to the DNN website.
5. A “BuildPublisher” sends the code from the source directory to the DNN site (D:\DNNSites\ClientDevSite\DesktopModules\CustomDNNModule as example).
6. Results of “build” are visible in the CruiseControl.Net Web Dashboard.
    

Implementing CI for DNN Development

Development:

We started DotNetnuke 4 development using the WSP methodology for all of our DNN projects. This has been successful for us for quite a while, especially when using EntitySpaces for the Persistence Layer and Business Objects (it's so easy using ES to generate the DAL. You must check this out if you are not using it). However, we found that to make this work we have to use WAP projects. I have a very fast laptop, but using WSP and doing a build of all of DNN to compile a module can be quite time consuming, taking several minutes sometimes. But, building a WAP project is FAST, saving some development time when debugging and testing builds, especially when doing those final little tweaks. One could argue that WSP is better, but for our setup with one to many developers working on a single module, WAP is the best decision. So, it did not take much to twist our arm to changing our methodology. It is unfortunate that in order to use this for our existing clients and projects, we will need to convert our WSP modules to WAP. But, we have started developing all new modules as WAPs and converting WSP modules to WAP is not a difficult task.

To read about the great WSP versus WAP debate, see the following links:

Shaun Walker’s post on WAP

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/434/Default.aspx

An interesting debate between Michael Washington and Vladan Strigo

http://www.dotnetnuke.com/Projects/ModuleNews/Forums/tabid/953/forumid/111/threadid/91268/threadpage/6/scope/posts/Default.aspx

WAP Methodology

“Web Application Projects provide a companion web project model that can be used as an alternative to the built-in Web Site Project in Visual Studio 2005. This new model is ideal for web site developers who are converting a Visual Studio .Net 2003 web project to Visual Studio 2005. (Released May 8, 2006)” - http://msdn2.microsoft.com/en-us/asp.net/aa336618.aspx

Michael Washington has a great post on creating a DNN WAP Module:

http://www.adefwebserver.com/DotNetNukeHELP/DNN4_WAP/

Once the module is ready for testing on our client development site, we use TortoiseSVN to “commit” code to Subversion (http://tortoisesvn.tigris.org/).

Source Code Version Control:

We use Subversion for our source code repository and version control system (http://subversion.tigris.org/). We have tried Visual SourceSafe and CVS, but have been using Subversion with success for quite some time now. CruiseControl.Net integrates with Subversion easily. It is also nice that there is a plugin for Subversion that allows us to send our comments directly to Gemini (project management/tracking application) when we commit new code.

Continuous Integration Software:

We use CruiseControl.Net, a .Net port of the Java based CruiseControl 

Continuous Integration Server using CruiseControl.Net

The CruiseControl.Net Server automates the integration process by monitoring the team's source control repository directly. Every time a developer commits a new set of modifications for the DNN module, the server will automatically launch an integration build to validate the changes. When the build is complete, the server notifies the developer whether the changes that they committed integrated successfully or not.

CruiseControl.Net allows for several different types of “Tasks”, such as:

• EmailPublisher (for emailing of build details)
• ExecutableTask (for kicking off executables, such as our custom assembly publisher)
• NAntTask (for unit testing)
• NUnitTask (for unit testing)
• RSSBuildsPublisher (for generating a RSS feed with details)
• VisualStudioTask (for running something in VS)
• Etc.

Here is an example ccnet.config:
<!--<ccnetconfig><configurationVersion>1.2.1</configurationVersion></ccnetconfig>-->
<cruisecontrol>
  <project name="BPLWantList">
    <workingDirectory>D:\cibuilds\ProjectName\ModuleName</workingDirectory>
    <webURL>http://ourCIdomain.com/server/local/project/ModuleName/ViewProjectReport.aspx</webURL>
    <sourcecontrol type="svn">
      <trunkUrl>svn://localhost/ProjectName/ModuleName</trunkUrl>
    </sourcecontrol>
    <triggers>
      <intervalTrigger name="Quarter Hour Build" seconds="900" />
    </triggers>
    <tasks>
  <exec>
      <executable>VenexusAssemblyPublisher.exe</executable>
      <baseDirectory>D:\</baseDirectory>
      <buildArgs>"d:\Source\ProjectName\DesktopModules\ModuleName\obj\Debug" "d:\DevSites\ProjectName\bin"</buildArgs>
  </exec>
    </tasks>
    <publishers>
      <buildpublisher>
        <sourceDir>D:\cibuilds\ProjectName\ModuleName</sourceDir>
        <publishDir>D:\DevSites\ProjectName\DesktopModules\ModuleName</publishDir>
  <useLabelSubDirectory>false</useLabelSubDirectory>
      </buildpublisher>
      <xmllogger />
      <statistics />
    </publishers>
  </project>
</cruisecontrol>

CruiseControl.Net Web Dashboard

The CruiseControl.Net Web Dashboard Application is used for reporting a wide range of information about the builds. At one end of the scale it reports summary details of all projects in your organisation and at the other it can give specific metric output for any specific build.

Here is an example of a simple DNN Module being used in our CI environment:

Notice the failed build notification. While we have not setup unit testing, you can see in the left menu in the image, there are quite a few different options.

Conclusion

For long term DotNetNuke module projects, setting up a continuous integration environment will save a tremendous amount of time in the long run. All of the tools to implement CI are free, lowering the total cost of DNN module development. With a little bit of time setting up your environment, you can provide continuous updates to your clients, all while forcing good coding practices among your developers. 
 

• Scheduled Task

• Search Admin

                    The search admin is for setting the maximum word length, minimum word length, option to include common words, and the option to include numbers. 

• Search Input Module

• Search Results Module

• Scheduled Task

• Search Engine Admin Module

• Search Input Module 

• Search Results Module

• Seamus Module

• Search Module

Feature Comparison Matrix:

Below you will find a list of features for DNN Search, Open-SearchEngine, Venexus Search Engine Standard, and Venexus Search Engine PRO.

 

DNN 4.5 was released today after a small delay last month. 

"A highly focused three month release cycle results in DotNetNuke® 4.5, a new release with integrated Microsoft ASP.NET AJAX support, a web-based installer, and a variety of other high value enhancements designed to improve the user experience." - DotNetNuke Enriches User Experience

I decided to try out a new install, before we perform any upgrades. So, after creating a new database, creating a new directory on the webserver for the site and changing permissions, setting up new site in IIS, and changing the web.config for the connection string, I tried loading the site. I had heard about the new installation wizard and was presented with the following:

I decided to do a custom installation so I could see all of the options.

One of the most common issues people have trying to install DotNetNuke is setting the file/folder permissions. It is nice to see the wizard test these.

Another big issue people have installing DotNetNuke is making sure the connection string is valid. The wizard also supports a database connection test.

Easy install so far....

Nice! You can now configure the host account instead of relying on the defaults.

You can also filter which modules get installed during installation.

And set admin user account and portal porperties instead of using the defaults.

You can also have optional skins and containers to be installed, if available.

And language packs if needed.

And done!

I am very impressed with the new installation wizard. It is good to see checks being performed that will undoubtedly decrease support issues for people who have not setup everything correctly.

After logging into the new site, the first thing I noticed was the different icons.I like the new and clean look of these icons. I also LOVE the new "Show Control Panel" dropdown option.

Something new too is the "Solution Explorer":

This is a convenient interface to the DNN Marketplace. The "DotNetNuke" and "About" tabs still appear to be in beta mode however. It should be interesting to see how this piece develops.

It is very exciting to see this new release, and I will post later how the upgrades go.

We did a search engine optimization (SEO) campaign for a client a while back that required us to setup a few new domains with blogging software. We used a variety of different blogging software  and noticed something very interesting...sites that performed pinging were crawled within 1-3 days and indexed within 2 weeks. All of the domains we used were brand new. In some cases, keywords that we were focusing on were in top 10 search results in 2 weeks as well. Needless to say, the client was happy.

So, we added a pinging feature as part of our DotNetNuke search engine module. Seamus, our search engine aggregation module, generates a RSS feed for the entire DNN portal. Anytime a tab/page is added or updated and Seamus finds this change, if the "Pinging Service" is enabled, it will ping 14 different blog and feed aggregation services.

So you are probably asking how does this work. Well, we send a "ping" to these aggregation services using XML-RPC. It simply tells these services that there is new content available on your site and to check the RSS feed. These services then will consume the feed and add it to their index. This provides a contextual link (assuming you actually use good titles for your pages) from these service sites directly to the content on your site. Pretty cool, huh?

Currently the following services are pinged with our module:

1. BlogDigger.com
2. BlogFlux.com
3. Blogsearch.Google.com
4. BlogRolling.com
5. Bulkfeeds.net
6. Feedburner.com
7. Feedster.com
8. IceRocket.com
9. Pingomatic.com
10. Syndic8.com
11. Technorati.com
12. My.Yahoo.com
13. Weblogs.com
14. Weblogalot.com

As a test, we dropped our search engine module on a new domain on 3/16/2007. With no links from external sites pointing to this domain, most if not all of the traffic was from our development at this point, averaging about 3-5 unique visitors a day (probably me, the client, and one or more of our developers). As of yesterday, the site had almost 150 unique visitors. Not bad for 2 weeks, considering we have done nothing else to this site other than add 10 total pages of content. This site is off to a great start and we have not even started a linking or submission campaign. See the graph below:

Also, checkout the following post on Marketing Pilgrim about faster indexing through pinging Google blog search that collaborates our results.

Ready to see the power of pinging blog and feed aggregators? Add a pinging service to your DNN site and watch the traffic roll in.

We issues a patch release today for the Venexus Search Engine, a DotNetNuke search engine module. This release has a few minor bug fixes and tweaks:

• Catalog creation in SQLDataProvider file moved to Search module (you still have to run the VenexusSearch module SQLDataProvider file through Host > SQL during new installation, but not for those who are upgrading).
• Queue Importance added to allow some URLs to be crawled sooner than others. If you are running a global search engine, we now give preference to certain domain extentions (.gov and .edu).
• Stores single Robots.txt file for domain instead of historical. Previously we stored a new robots.txt for each weekly check if it was updated. Now we only store one.
• Feed Title is now the portal/site name.
• Added XML-RPC ping for BlogFlux inclusion in our blog/feed aggregator pinging service. We had to remove one aggregator and added BlogFlux to the list (14 total)

Get the free version of our DNN search module.

There is nothing better to start off the day than having a client running into a 100% CPU utilization issue on their production SQL Server. Every few minutes, the server would spike up and hang there for a variable amount of time (15 seconds to several minutes). You can only imagine the flakiness of a website with SQL Server choking to death. There was nothing of value to point any fingers as to the culprit of this issue in the event logs for DNN (Admin > LogViewer)...none that we saw through a brief spot checking and filtering of event types (this was incredibly slow and seeing timeouts so we abandoned all hope of using DNN Admin/Host tools to find the problem).  And, there was not an alarming number of events actually logged in EventLog table. However, we have seen issues with performance that are usually resolved by clearing the Log Viewer. We have seen cases where clients who have high traffic/usage sites, or a broken/problematic module on all pages, have 5 and 6 figure rows of data for EventLog table, especially if all the default settings are used for the DNN Log Viewer settings. We have seen timeout issues just trying to clear the event log when they get that large ("Delete EventLog" as the sql statement does the trick quickly from SSMS). So, we went ahead and cleared it, but the issue persisted.

For those who have not explored much in SQL Server Management Studio (not in SSMS Express), there is now a Database Engine Tuning  Advisor and SQL Server Profiler (under Tools > SQL Server Profiler). Running the SSP, we performed a trace and caught the offending SQL causing all of the havoc. Just a note...we have run DETA to find recommendations from trace files for several large DNN databases and apply the recommendations (it usually creates new indexes for tables that have 6 and 7 figure rows, helping greatly with performance on databases). But in this case, we just started and stopped the trace in SSP before and after a huge and hanging spike. Going through the rows looking for CPU hits, we found the following 2 villians of resources:

I am concerned about why 6000 rows of data would be taking such a hit on cpu resources. However, that it more records than I believe should be there, so lowering the defaults will help. Nothing in the DNN stored procedure for GetSchedule really stands out at me as being problematic, nor at first glance do I see anything that could be changed that may help, but I will ponder on this some more in my copious spare time.

So, if you are having trouble with SQL Server performance and DNN, check and make sure you keep your EventLog and ScheduleHistory purged.

If you need help, be sure to checkout our DNN Support Packages.

We ran into an issue parsing some HTML for a DNN content migration project we are working on. We needed to find the actual content of the page, without all of the look and feel. Luckily we found a pretty solid case of an opening and closing div tag that wrapped the entire content of the page. At first we had a basic regular expression for finding the div tags like so:

After some digging, the following regex does the trick:

We released the latest version of our search engine module last week. It has all of the features I mentioned in my previous post, plus the ability to add excluded URLs and partial URLs.

Here are the new specs:

Items marked with * are new

Features	Standard Version	Pro Version
Seamus Features
Maximum # of Pages	500	Unlimited
Install on commercial site	No	Yes
Scheduled Index Updates	Yes	Yes
Announcements Module Support	Yes	Yes
Contacts Module Support	Yes	Yes
Events Module Support	Yes	Yes
FAQ Module Support	Yes	Yes
Links Module Support	Yes	Yes
Text/HTML Module Support	Yes	Yes
Index MS Excel Documents *	No	Yes
Index MS PowerPoint Documents *	No	Yes
Index MS Word Documents *	No	Yes
Index PDF Documents *	No	Yes
Index Rich Text Files *	No	Yes
Global Crawler *	No	Yes
Allows users to add feeds	No	Yes
Custom User Agent	No	Yes
Obeys Robots.txt	Yes	Yes
TTL Support	Yes	Yes
Feed and Queue Aggregation Using AJAX	Yes	Yes
Display Top X Latest Items	Yes	Yes
XSLT Support	Yes	Yes
Latest Items RSS Feed Generation	Yes	Yes
Portal Specific Feed	Yes	Yes
Enclosure/Podcast Support	No	Yes
Pinging Service	No	Yes
Exclude URLs *	Yes	Yes
Search Features
Search Skin Object	Yes	Yes
Use Image or Text for Search button	Yes	Yes
and - (AND and OR) Support	Yes	Yes
Quoted Search Support	Yes	Yes
Keyword Highlighting	Yes	Yes
Obeys DNN Security	Yes	Yes
Social Bookmarking Support *	No	Yes
Support
Issue Tracker	Yes	Yes
Email	No	Yes
Phone	No	1 Call
Price	Free	$199 Per Year

 

You can download the free version here.

We have released the new version of the Venexus Search Engine. VSE Standard Version 1.1.0 has several bug fixes and shows some of the new features of the Pro version.

New standard features and bug fixes:

• VenexusSeamus - Changed TransformXSL to not create a temporary XML file
• VenexusSeamus - Modified Response.Charset
• VenexusSeamus - New Delete Tabs routine for removing deleted and expired tabs
• VenexusSeamus - Ability to reload default XSLT file
• VenexusSeamus - Shows total number of aggregated items
• VenexusSeamus - Gridview pagination
• VenexusSeamus - Link from Grid to show aggregation errors
• VenexusSeamus - Guid attribute added
• VenexusSeamus - application/rss+xml support
• VenexusSeamus - Automatic creation of fulltext index during installation (works for SQL Server Express too!)
• VenexusSearch - Support for DNN 4.4.1 and "search" URL parameter
• VenexusSearch - Non-authenticated postback issue resolved
• VenexusSearch - Limits URL length for display
• VenexusSearch - Quoted query support

If you have any issues with installation, configuration, or bugs, pleas post them in our issue tracker.

The first beta testers of the Venexus Search Engine were the guys from True Lawyers. They created a new portal in their DNN installation for Search.TrueLawyers.com. Search.TrueLawyers.com is a legal search engine. Their instance of VSE has aggregated over 216,000 legal articles, news, and related site pages as of this morning. You can test this site and see that the speed of VSE is still great when considering the amount of data it has already indexed. When using the site, each time a page is loaded that has Seamus on it (and Seamus CAN be hidden on the page), 5 feeds are aggregated. Any new items in the feeds are added to the index immediately. While the user sits on the page, AJAX is used to pull more feeds. Plus, since the site is new and does not have much traffic...yet, they use a RSS reader to call the Seamus RSS feed, which grabs more data every 10 to 15 minutes. As you can imagine, their index is growing FAST! You can see the latest items Seamus has aggregated by visiting the True Lawyers Legal News Room.

So, not only does VSE work as a site search engine and multiple portal search engine, it also works as a full blown search engine, aggregating items from your DNN installation, as well as other sites that provides RSS feeds. One of the features we are working on for the 1.1 Pro version is the ability to index any website, regardless of having a RSS feed. You can now have the ability to build powerful niche websites that provide your users with lots of relevant information.  Plus, with the RSS feed Seamus generates, you can set it to display items for only your website, allowing you to submit the link to many feed directories, providing search engine optimization. The 1.1 Pro version will ping many blog directories, greatly increasing traffic to your website, treating your entire website like a blog. And we all know that the other search engines are just eating up blog content, increasing the page rank of those sites over many traditional websites without feeds. Ready to try it out? You can download the release candidate here.

Stay tuned for more...

UPDATE 2/7/2007:

I just checked the total items indexed for this site again and it is now showing over 246,0000 items. So in 2 weeks, an extra 30k + items were indexed.

I know many of you have been patiently waiting for the release of the Venexus Search Engine. We have had several beta testers try out previous release candidates, and have several new tweaks in this release.

Seamus Additions:

• Web.configless (No changes to web.config needed. Beta Testers should remove EntitySpaces web.config entries when installing this version)
• Object Qualifier support (Thank you Barry White for testing this)
• Index current tab (Seamus will index the tab it is on. You can add make Seamus invisible on the page by showing 0 items in the feed and unchecking Show Feed. Add to all pages on the site and Seamus will index and update the index when the page is updated)
• Edit Feed Display (Only show feeds selected in Edit Feeds section. By default, all are show. Selecting feeds will filter news display of only items indexed from the feeds list)

Search Additions:

• Web.configless
• Object Qualifier support
• "query" URL parameter (You can now use your existing default DNN search results page. Simply drop the module on the search results page and remove the default search results module. Utilize the DNN Search textbox in your skin with the power of Full-Text Indexing).
• Search form skin object support (see instructions)
• Form post fix (A fix was added that allows you to simply hit the enter key after adding your query, rather than forcing you to click on the button)
• Allow user selected web or site search (allow your users to select whether their search is against the current portal or for all search results in the database)
• URL Trim (Used to trim the URL display in the search results. Long URLs would stretch out the skin)
• Search Query (Saves user queries and the number of "hits" for that query. This will be used in the pro version for "Top Searches" and "Latest Searches".)

Here is some information about our DotNetNuke search engine module. You can test it on our site here. We also have the latest version loaded on our DNN search site for finding DotNetNuke related pages and sites.

As for the official release, we are waiting on FlatBurger to fix an issue with their code protection that causes the module to generate an error after activation. We have been told that this may be fixed by Friday...we will see. In the meantime, please send us your thoughts on this release candidate. If you find any bugs, please post them to our issue tracker. If you have any suggestions for new features, please post them in the issue tracker or in the support forms.

REQUIREMENTS FOR VENEXUS SEARCH ENGINE

• DotNetNuke 4.3.5 or Higher (Yes it works with the DNN 4.4 release)  
• SQL Server supporting Full-Text Indexing
• .Net full trust for EntitySpaces and Reflection usage

Now for the files....

Before installing this, you MUST read the instructions. You CANNOT just install both modules and expect it to work. You MUST configure fulltext indexing manually to get this to work. You will find instructions on performing this action in the Search Instructions and Configuration.

You can download both modules here. The file is also attached as an enclosure.

Please post your links here in a comment to show everyone how you are using the Venexus Search Engine.

UPDATED: Link to module downloads has been updated.

In case you were wondering from my last post, here is how to get a list of all modules by Portal:

SELECT DISTINCT ModuleDefinitions.ModuleDefID, ModuleDefinitions.FriendlyName, Modules.PortalID
FROM         ModuleDefinitions CROSS JOIN
                      Modules LEFT OUTER JOIN
                      Modules AS Modules_1 ON ModuleDefinitions.ModuleDefID = Modules.ModuleDefID
WHERE     (Modules.ModuleDefID IS NOT NULL) ORDER BY Modules.PortalID

Here is how to specify a specific portal in the installation:

SELECT DISTINCT ModuleDefinitions.ModuleDefID, ModuleDefinitions.FriendlyName, Modules.PortalID
FROM         ModuleDefinitions CROSS JOIN
                      Modules LEFT OUTER JOIN
                      Modules AS Modules_1 ON ModuleDefinitions.ModuleDefID = Modules.ModuleDefID
WHERE     (Modules.ModuleDefID IS NOT NULL) AND (Modules.PortalID = 0)

We needed to check which modules were NOT being used on a DNN site. Why? It's a multi-portal DNN 3.1 website with quite a few 3rd party modules on it and we wanted to know which modules were not in use so we could remove them from the DNN installation before performing an upgrade. No need to add extra compilications or search for module updates for modules that were not being used. And if they are not being used, why leave them on there adding to the bloat? Anyway, here is the SQL:

SELECT     ModuleDefinitions.ModuleDefID, ModuleDefinitions.FriendlyName, ModuleDefinitions.DesktopModuleID
FROM         ModuleDefinitions LEFT OUTER JOIN
                      Modules ON ModuleDefinitions.ModuleDefID = Modules.ModuleDefID
WHERE     (Modules.ModuleDefID IS NULL)

I never got around to making an announcement that DNN 4.3.6 was release a couple of weeks ago....now DNN 4.3.7 is out.

I checked the security announcements and only saw 2 issues that were already fixed with DNN 4.3.6:

DNN 2006-4-C (16 November 06)

DNN 2006-5-L (16 November 06)

I am not sure if this is the 4.4 release Shaun Walker mentioned in his blog yesterday, or this is in fact the 4.3.7 release. The change log in the bug tracker does not appear to have any related info on 4.3.7. However, the roadmap for DNN 4.4 release shows many items checked in.

	Component	Issue Type	Issue ID	Summary	Resource	Status
(4.4.0) Performance Release	Admin / Host Functions	Bug	DNN-4492	ModuleTitle in multi definition modules		Checked-In
	Admin / Host Functions	Bug	DNN-3868	Page Head tags are not properly processed		Checked-In
	Admin / Host Functions	Bug	DNN-4011	Action Menu with Module Specific Permissions is not displayed		Checked-In
	Admin / Host Functions	Bug	DNN-4476	Cannot use icon from module directory in action buttons		Checked-In
	Admin / Host Functions	Enhancement	DNN-4503	Improve Delete Portal Functionality		Checked-In
	Admin / Host Functions	New Feature	DNN-4496	Add User Quota		Checked-In
	Admin / Host Functions	New Feature	DNN-4502	Improve Portal Management		Checked-In
	Admin / Host Functions	New Feature	DNN-4504	Add a new Delete Expired Portals action		Checked-In
	Admin / Host Functions	New Feature	DNN-4495	Add Page Quotas		Checked-In
	Localization / ML	Bug	DNN-4273	Collation issue with Event Log		Checked-In
	Localization / ML	Bug	DNN-4506	Pop-up calendar localized date format bug		Checked-In
	Localization / ML	Bug	DNN-4483	Localized images break when using the "ShowMissingKeys" app setting.		Checked-In
	Localization / ML	Bug	DNN-4560	Popup calendar		Checked-In
	Localization / ML	New Feature	DNN-4520	Force a specific language for first visitors		Checked-In
	Performance	Bug	DNN-4086	Performance: Reduce Database Calls		Checked-In
	Performance	Bug	DNN-4088	Performance: CBO and Reflection		Checked-In
	Performance	Bug	DNN-4090	Performance: ClientAPICaps.config caching		Checked-In
	Performance	Bug	DNN-4092	Performance: XmlSerializer		Checked-In
	Performance	Bug	DNN-4087	Performance : TabCache		Checked-In
	Performance	Bug	DNN-4091	Performance ; Menu providers		Checked-In
	Performance	Bug	DNN-4093	Performance: XPathDocument vs XmlDocument		Checked-In
	Performance	Enhancement	DNN-537	Imporve Startup performance		Checked-In
	Performance	Enhancement	DNN-662	Implement HTTP compression		Checked-In

Since 4.4 is called a "Performance" release, and on the website it says 4.3.7 is a stabilization release, I take it that they are indeed different. I just would like to know what was changed in the 4.3.7 if indeed it is a stabilization update.

At some point earlier this year, DNN Find became a different mission. We decided to build a full blown search engine for DotNetNuke. Not one that would just index a single DNN site, but one that would allow you to index all portals in a DNN installation AND information from external sites. And how would external site indexing best be handled? …via RSS feed aggregation of course.  

Seamus is the first of the two modules that make up the Venexus Search Engine. SEAMUS = Search Engine Aggregation Module Utilizing Syndication. On a side note, there is also an obscure Pink Floyd song that not many know from the Meddle album, about an old hound dog by the same name. Our hound dog “fetches” data and stores it to a table that has enabled MS SQL Server full-text indexing. But before I go into the specifics, I think it is important to know about the framework.

We started with traditional DotNetNuke module development…until EntitySpaces was released. I’m an old ASP/VB developer and personally, it took me a bit to get my head wrapped around how ES worked, but once I figured it out, I was hooked. ES saves the day by automagically generating all the CRUD (create, read, update, delete). While very similar to the logic of a BusinessController and InfoObject, ES uses Collections and Entities. But, where I found ES the most useful is the Dynamic Queries you can write directly into the business logic.

For example, in Seamus we need to check the domain to see if it matches one we are already indexing:

            Dim colDomains As New VenexusDomainCollection
            colDomains.Query.Select(colDomains.Query.DomainName, colDomains.Query.DomainID)
            colDomains.Query.Where(colDomains.Query.DomainName.Equal(GetDomainName(sURL)))
            colDomains.Query.Load()
            If colDomains.Count > 0 Then
                     ‘a bunch of removed logic goes here..
            End IF

With the colDomains.Query.Select, we are only returning the data we need rather than all columns. With the colDomains.Query.Where, I eliminated the need to:

1. Write a stored proc just to retrieve by DomainName
2. Iterate through the entire table, every row of all domains, just to find the one I am looking for.

I won’t even go into the performance gain of not having to loop through those rows of all columns, nor the time (even though it would be simple) to write a stored proc to pass in DomainName and have it return the DomainID.

Here is an example of adding a record to Seamus for a new feed:

         Dim entFeed As New VenexusSeamus
         entFeed.AddNew()
         entFeed.Url = txtURL.Text
         entFeed.Title = txtTitle.Text
         entFeed.Account = txtAccount.Text
         entFeed.Password = txtPassword.Text
         entFeed.CacheTime = txtCacheTime.Text
         entFeed.FeedTimeOut = txtTimeOut.Text
         entFeed.DateAdded = Now()
         entFeed.DateUpdated = "1/1/1901"
           If chkActive.Checked = True Then
              entFeed.IsActive = True
            Else
                entFeed.IsActive = False
            End If
         entFeed.Save()

Easy enough, eh?

And here is an update of a feed for Seamus:

    Dim entFeed As New VenexusSeamus
    entFeed.LoadByPrimaryKey(hidRSSID.Value)
    entFeed.Url = txtURL.Text
    entFeed.Title = txtTitle.Text
    entFeed.Account = txtAccount.Text
    entFeed .Password = txtPassword.Text
    entFeed.CacheTime = txtCacheTime.Text
    entFeed.FeedTimeOut = txtTimeOut.Text
    entFeed.DateAdded = Now()
    entFeed.DateUpdated = "1/1/1901"
          If chkActive.Checked = True Then
              entFeed.IsActive = True
          Else
                entFeed.IsActive = False
          End If
    entFeed .Save()

And a delete example:

    Dim entFeed As New VenexusSeamus
    entFeed.LoadByPrimaryKey(hidRSSID.Value)
    entFeed.MarkAsDeleted()
    entFeed.Save()

Yeah, it’s that easy. Makes you want to fire up your IDE eh?

Sure, I have used DAL Builder Pro, which was a huge time saver, but EntitySpaces made me to never want to develop any other way. Plus, last I checked, DAL Builder Pro was still only for DNN 3 development. The ease of generating the DAL and the ability to easily REgenerate the DAL if the database schema changes, makes ES the tool of choice for all of our module development. I cannot even begin to count the hours I have previously spent hand coding changes in a DAL due to spec changes. Oh how I wish I had all those hours back!

With the new DNN admin grid templates, it is just ridiculous how much code is generated before having to write the first line. The new template will generate an editable grid of the table(s), with sorting, paging, and search. If you are interested in .Net development (this is not just a DNN tool, it works for all .Net 2.0 development and using C# or VB.Net), you must check it out.

NOTE: Just so you know, we do not have any affiliation or partnership with EntitySpaces, we just think their tool rocks.

So, even though we had much of the initial Seamus development completed, we scrapped it and started development with ES. This will make future modifications and additions so much easier, saving time in the long run.

With that said, here is how Seamus works…

After you install Seamus, you can go into the module settings:

So in this example, the display for Seamus should show the top 10 items last indexed, each with a link to the actual item in the Title and using the “…More” link. A feed icon will also be displayed that provides a link to a RSS feed for the top 10 items.

Here is an example of the display:

Now while the above example does not show any local items (tabs or modules from this site), it does have items indexed from other sites. All of these items were from RSS feeds that were aggregated. As a module editor, you have the ability to manage external feeds (or local feeds if so desired, but we will go into more detail about how Seamus works shortly). But, if there were local items visible, they would only be visible if you have the proper permissions. Seamus checks permissions on any local site at the module and tab level for the display and the RSS feed. 

Here is an example of the feeds we are are currently indexing on the Venexus Search Engine:

Here is the interface for adding new feeds:

Now we will get into how Seamus works…

First off, on the first load of Seamus, a dump of data from all modules supporting the IPortable interface (currently limited to DNN Core modules) is performed to ensure that there is data in the index. And every X hours (determined in module settings), the index is checked for new, updated, and deleted pages/modules.

Secondly, any feeds that have been added to Seamus are aggregated 5 at a time, order by last updated.  And, while the user is sitting on the page, every 30 seconds that pass, 5 more feeds are aggregated via AJAX. This user interactive aggregating decreases the load on the server, rather than running as a scheduled task like the core DNN Search.

In order to save bandwidth, and to not tick off the owners of the websites you are aggregating data from, Seamus has what I call “smart caching”.  Each time a feed is requested, if the information in the feed as not been updated, Seamus will increase the cache time. If the feed has been updated, it will request the same feed sooner than it had previously, decreasing the cache time. Over time, and based on the “average” a feed it updated, Seamus learns when to check again for updates, all while obeying TTLs.

Seamus will also index the current page/tab it is sitting on. Now you may be asking why you would index a page that displays items that have already been indexed. Well, Seamus can be setup to not display the top X items and/nor the RSS feed. Here is an example:

With the above Seamus settings and the module settings to display on all pages and set to not display the container or using an “invisible” container, when a user lands on any page of the site, the page is indexed. You can index your entire site by letting the users "crawl" the website. Also, when the page is updated, the index will be updated. Here is the module settings example:

So, not only does Seamus index all portals in the DNN installation by doing a dump of all modules that support the IPortable interface and individual page indexing based on user interaction, it will also aggregate and index data from other sites. This gives you the ability to create a full blown search engine for your niche. For example, let say you have a website about racing. You could have your entire DNN site indexed, along with aggregation of more racing data from the following sites:

http://www.sportsline.com/partners/feeds/rss/auto_news

http://rss.news.yahoo.com/imgrss/events/sp/042103autoformula

http://rss.cnn.com/rss/si_motorsports.rss

Not only are you able to display a list of the last items indexed in order to keep a page from becoming stagnant, you can also provide a RSS feed for your users, giving them a reason to return to your site. I will save a Seamus and SEO discussion for another time, but here is an example site for a legal search engine.

Speaking of time, I am once again out of it. Part III will be a discussion of the second module, the search form module. Stay tuned...

The news is out, DotNetNuke is going corporate. Perpetual Motion Interactive Systems, Inc., started by Shawn Walker, has been managing the DotNetNuke Project. According to a press release on the DotNetNuke website today, the formation of DotNetNuke Corporation in Seattle, Washington will "serve the growing needs of the project and its ever-expanding community".

This is indeed big news! At this time I am not sure whether to be excited or worried. While I understand the past year has been challenging, with such a huge adoption rate of the project among all types and sizes of business entities (we have seen this first hand), and has brought in the extra administrative burden to the core team, I had hoped that there was a plan to offset the growth. With any "open source" project, people immediately think "free" which has been the downfall of many projects IMO. In any business model, 0 times 0 is still 0. And let's face it, people just can't afford to work for free. While I am grateful for the core team and their many volunteer hours, and I for one am unable to devote such hours, I do feel these people should be compensated for their hardwork. I felt DotNetNuke was on the right path with the Benefactor program (we joined within hours of its announcement) and with the announcement of providing 3rd party module reviews and a 3rd party marketplace, I felt it was bound to gather the dough required to float the venture. But the idea of DotNetNuke going corporate has changed the possibilities greatly.

From the article:

“DotNetNuke Corporation is not a typical commercial entity,” Walker added. “Rather, it is dedicated to the public benefit goal at the heart of the DotNetNuke project, which is to create opportunities and spread entrepreneurship to the world by providing a superior Open Source web application framework."

AND...

In addition to spearheading the Open Source project, DotNetNuke Corp. will also focus on developing and delivering services which support the ecosystem, including marketing, sponsorships, and a wide range of partner-related activities. These activities are expected to generate revenue, but the company intends to focus on those opportunities that are consistent with the community values and public goals of the project, Walker said. This includes providing funding for aspects of the project that are difficult or challenging for volunteer teams to solely undertake such as professional marketing, large-scale platform and feature development, product certification and ecommerce initiatives, he added.

With that said, it seems to say, DotNetNuke is going corporate so that they can fund the development of additional activities that need more funding. Now one has to consider the rumors that have been flying about the changes in DNN 4.3 related to membership, and the mysterious source that funded these changes. Also, is there a reason for making the headquarters in Seattle, Washington? To get closer to Microsoft maybe? How will the business model change, or will it? Will DotNetNuke eventually be sold? I think there are still lots of questions in my mind about the reasoning for this move, but we all know the answer...$$$. I am not saying any of the items above are a bad thing. Afterall, anyone who complains about Microsoft being a monoploy is just jealous of a beautiful business model. At the same time, in the words of Google, "Don't be evil", should be taken to heart.

I want to think that this will be the big push DotNetNuke needed to get into the limelight, but only time will tell. In the meantime, we will be keeping busy with the many clients Venexus has accumulated over the last couple of years, all due to a little CMS called DotNetNuke. We can't thank DotNetNuke enough for our own business growth, and hope the new path is one that will continue to benefit the ecosystem and community and allow DotNetNuke Corporation to prosper.

Wow, we can't even keep up with all of the new releases of DotNetNuke lately... Download DNN 4.3.4

Digging a little deeper I see the reason for this quick build is due to a couple of security issues, one being a "Critical Issue".

DNN 2006-1-M (02 August 06)

DNN 2006-2-C (02 August 06)

I also found a page on DotNetNuke that I have not seen before:

http://dotnetnuke.com/SecurityPolicy/tabid/940/Default.aspx

At the bottom are a couple of documents:

Security Documentation

Title Owner Category Modified Date Size (Kb)   Secure Module Development Shaun Walker   7/21/2006 274.41 Download Hardening DotNetNuke Installations Shaun Walker   7/21/2006 274.46 Download

Can't we go back to complaining about when the next release will be? Just kidding. It is good to see that the core team is proactive about keeping DNN patched and up-to-date. As a community, we need to do the same and update our systems as quickly as possible to keep DNN from getting a bad name.

Shaun Walker has posted a feature matrix comparison of DotNetNuke versus ASP.NET 2.0 versus SharePoint Server 2003 ( SPS 2003 ) versus Microsoft Office Sharepoint Services 2007 ( MOSS 2007 ). This is a great breakdown of features showing the differences between the platforms and should help anyone who is trying to pitch DotNetNuke to the "decision makers".

DNN 4.3.3 was released yesterday. We have our fingers crossed for this version! Stay tuned...

This has been an exciting month for DotNetNuke with over 300,000 registered users and the release of DotNetNuke 4.3. The new features in DNN 4.3 rock! And, offer many new features and functionality over its predecessors. While the new release is not without some new issues, and we do not believe this release is stable enough to be considered a production release, it does offer much promise into the future of DotNetNuke as it begins to catch-on with upper management (more on this later). If you just take a look at the number of downloads of DotNetNuke, there is a steady curve that leaves us all optimistic.

Date (UTC)	Downloads	Bytes Served
Jun 2006 *	99,379	667.2 GB
May 2006	72,360	423.2 GB
Apr 2006	70,736	411.4 GB
Mar 2006	81,935	480.8 GB
Feb 2006	84,530	492.9 GB
Jan 2006	93,425	547.6 GB
Dec 2005	111,006	651.2 GB
Nov 2005	150,077	891.7 GB
Oct 2005	43,193	256.2 GB
Sep 2005	38,540	303.8 GB
Aug 2005	38,103	354.8 GB
Jul 2005	43,292	462.6 GB
Jun 2005	60,881	592.6 GB
May 2005	23,931	369.1 GB
Apr 2005	39,365	613.0 GB
Mar 2005	45,624	577.6 GB
Feb 2005	34,013	279.7 GB
Jan 2005	25,517	186.2 GB
Dec 2004	24,219	137.8 GB
Nov 2004	20,151	108.3 GB
Oct 2004	13,932	68.5 GB
Sep 2004	13,180	63.9 GB
Aug 2004	14,067	67.5 GB
Jul 2004	14,508	69.6 GB
Jun 2004	23,907	115.0 GB
May 2004	13,300	53.2 GB
Apr 2004	21,074	80.1 GB
Mar 2004	4,300	15.9 GB
Feb 2004	0	0 bytes
Jan 2004	133	199.3 MB
Dec 2003	117	175.3 MB
Nov 2003	74	110.9 MB
Oct 2003	331	495.5 MB
Sep 2003	341	509.9 MB
Aug 2003	318	476.6 MB
Jul 2003	351	524.3 MB
Jun 2003	66	96.7 MB
May 2003	3,814	4.7 GB
Apr 2003	4,187	4.5 GB
Mar 2003	372	334.6 MB
Total	1,328,649	9.3 TB

^* Partial data: End of month not yet reached

Figures authoritative as of:
SourceForge.net, tracker and forum data: 2006-06-28 09:50 UTC Download data: 2006-06-28 09:55 UTC Project Web: 2006-06-28 09:50 UTC

Source: SourceForge

It would be interesting to see the actual number of DNN sites in production, indeed.

We believe this trend will continue as businesses realize the power of the web application framework for their enterprise information portals (corporate portals, intranets, extranets, web presence, etc.). With the advantage of getting their existing static, or non-existant websites and intranets up-to-date with .Net 2.0 and SQL Server 2005, many companies are finding DotNetNuke an affordable solution when compared to other high priced content management solutions. However, one of the hurdles that must be conquered is the fact that most upper management (the ones who approve the budget and sign the checks), still cannot comprehend the ROI from building a corporate portal solution, with their "If it ain't broke, don't fix it" mentality, further digging themselves and their company into the dinosaur graveyard. Unfortunately, the developers have a hard time translating geek-speak to the uninitiated, which slows this process. But, with DotNetNuke being Open-Source, developers have an easier time to sell the idea to upper management, they just have to get the idea wrapped around their narrow brains...

So, we look forward to the coming months as DNN 4.3 progresses, adpotion of the application grows, and upper management evolve or retire. This is truly the Wild-Wild-West of content management systems for the masses.

Just when we were about to abandon ship on the 4.3 release and roll back to 4.0.3, a new "point release" is issued...

"A "point" release has been posted for DotNetNuke 3.3/4.3 today. This point release contains fixes for a number of issues which were identified in the original Release Candidate packages." - Download from DNN

With weird caching issues and missing UserController methods,...which I will rant about later...we were prepared to roll back our development stack to the 4.0.3 release. Instead we will be testing the new version with our fingers crossed that it fixes many of the issues we have found. Check back later for the results!

Many of us have been waiting for the DNN 4.1 release, instead we get the DNN 4.3 release!

Here is the announcement on the site: DotNetNuke® 3.3/4.3 Release Candidate Now Available

Here is a list of features that are in the new release:

Membership

- Provider Abstraction - create our own provider to abstract ourselves from the Microsoft provider.
- HttpContext - eliminate dependence on HttpContext
- ApplicationName - manage our multi-portal capabilities within DNN rather than trying to hack the Microsoft provider
- Question and Answer - the ability for a user to enter and store a private question and answer which can be used for a password reminder
- Hashed Passwords - hashed passwords are supported through the Microsoft Membership Provider. We should provide a mechanism to support hashed password in DNN as they are much more secure then encrypted passwords and do not rely on MachineKeys. ( It would be advantageous to make this the default but the side effect would be that we would no longer have a password retrieval mechanism )
- CAPTCHA - add the ability to display a small image with embedded text which bots can not read. Prevents brute force dictionary login attacks.
- Public Registration - the system should send an email to the user on public registration ( to prevent cases where another user registers with their email address ).
- Profile Change Notification - when any profile attribute is changed, the owner of the account should be notified ( using the original email address ). This is to alert people in the event that an unauthorized user has gained access to their account and made changes to their profile ( password, email ).
- Login Redirect - after login there should b a way to send a user to a specific page. This could be implemented at the portal or user level.
- Password Generation - the ability for an admin to automatically generate a secure password for a user on account creation
- User Account Creation Notification - when an admin creates a user account they should have an option to send the account details to the user
- Force Profile Update - ability to force a user to update their user profile ( implemented at a granular level based on required Profile fields )
- Force Password Change - ability to force a user to change their password
- Password Complexity - add the ability to define some passord complexity requirements ( ie. mixed upper/lower case, numeric and alpha-numeric, etc... )
- Password Length - increase the default minimum password length from 4 characters ( will require a more secure host password on initial install )
- Password Expiry - a mechanism for expiring a password which would force a user to enter a new password. This could be done through password aging parameters defined at the portal level ( ie. every 2 months ). Would likely need to be associated with a reminder email to let people know their password was going to expire ( a similar requirement is needed for Role expiry ).
- Display Name Field - the membership schema should store the DisplayName of the user for demographic purposes - this item is critical for international users where their name is not represented as "FirstName LastName". Modules should link to the DisplayName for audit purposes rather than using FirstName and LastName.
- Preserve Login Parameters - when a user is directed to the login screen, the system needs to retain the original url ( with parameters ) so that it can redirect back after successful login ( especially useful in nested module UIs like Forum )
- Logout Behavior - after logging out, the user should be able to remain on the same page rather than being redirected to the home page ( the only reason they are being redirected now is because they may no longer have access to the page because of roles - but this is largely unnecessary and can be handled other ways ).
- Automated Verified Registration URL - the email sent to user when using he Verified Registration process now containa a URL which a user can click to very quickly validate their account
- User Lockout Notification - enhance the user lockout ( 3 unsuccessful logins ) to send an email to the admin to notify them of the event
- Manage Users UI Consistency - both users ( register.ascx ) and administrators ( manageuser.ascx ) should be able to manage the profile properties consistently.

Roles

- Provider Abstraction - create our own provider to abstract ourselves from the Microsoft provider.
- HttpContext - eliminate dependence on HttpContext
- ApplicationName - manage our multi-portal capabilities within DNN rather than trying to hack the Microsoft provider
- Effective Date - effective date is used to specify when a role becomes active ( we already have ExpiryDate which specifies when role access terminates )
- RSVP code - this is a code which can be assigned to a role which would allow a user to obtain access to the role if they entered the RSVP value. A use case would be an administrator working with a group of users could send them an RSVP code which they could then enter on the site to get instant access, rather than the admin having to assign the users to roles manually.
- Avatar field - the administrator should be able to associate an avatar to a role.
- Role Groups - administration mechanism to group roles within the same portal to provide a faster, easier way to manage/assign them. This affects the Role Management, User Role management, and Permissions grids.
- Manage User Roles - once a site has more than 1000 users the user combobox, displayed when you access Manage User Roles from the Roles UI, contains too much data and sometimes times out. As a result there is no easy way to see the users who are assigned to a role ( the bottom portion of the UI ).


Profile

- Provider Abstraction - create our own provider to abstract ourselves from the Microsoft provider.
- HttpContext - eliminate dependence on HttpContext
- ApplicationName - manage our multi-portal capabilities within DNN rather than trying to hack the Microsoft provider
- Company Name Field - the default list of profile properties should contain the CompanyName of the user for demographic purposes
- Default Properties - In the default install we should provide a comprehensive collection of properties (consistent with W3C's Platform for Privacy http://www.w3.org/TR/P3P)
- Module Profile Properties - Modules should be able to add profile properties for module-specific information.
- Portal Properties - the Profile Properties should be defined at the Portal level (not the host level)
- Dynamic Definition - the Portal level properties should be managed by the Portal Administrator.
- Searchable - Profile Properties should be Searchable (ie we should be able to do Find Users By City or Find Users with Green Eyes)
- Profile Property Order - To support certain eastern cultures the order of Profile fields is important.
- Public/Private Data - the User should have the ability to specify which profile items are public vs. private. DNN should have the ability for anonymous users to link to a User Profile page and view public information.


Event Queue

- generic framework which allows managed code to create and consume custom events ( including parameters ). Events are persisted to the data store so they can survive app restarts.

File Management

- Storage Location - new Folder level specification to identify whether files should be stored on the file system ( unsecure ), file system ( secure ), or database ( secure ).
- File Manager - refactored to use the database as the source for file/folder information rather than the physical file system. Improved user interface to accomodate new Storage Location options as well as provide Synchronization at the folder level.
- File/Folder Association - added referential integrity between the Files and Folders table
- File Server - HTTP Handler for serving files regardless of Storage Location. Takes advantage of Folder permissions to ensure secure access to files.
- URLControl - leverage folder permissions and storage location in file selection and upload options.

Usability

- Copy Content - in Add Page, a new option which allows an admin to select a page and the granularly select the modules to copy as well as whether to make a New, Copy, or Reference.
- Page Template - template which defines a default set of modules to insert into the page when the page is added. The template is based on a portal template fragment and is currently defined at the host level. The default template provided contains a single HTML/Text module which helps address the usability issue of new portal administrators who do not understand that you  need to add modules to your page once it is created.
- Host Space - increased host space capacity from 999.
- Module Title Editing - enabled AJAX-style editing of the Module Title by default
- ClientAPI - fixes and enhancements to ClientAPI javascript library as well as navigation controls ( ie. treeview, SolPartMenu, DNNMenu )
- Navigation Provider - fixes and enhancements to Navigation provider library
- AJAX - fixes and enhancements to DNN AJAX library
- URL Rewriter - adjusted logic so that full URL can be used in rewriter rules.
- Rich Text Editor - added support for URLControl in hyperlink popup so that a user can select from a file, page, or external URL. Also added Insert Smiley option.
- Newsletter - added ability to enter From: address.

Framework

- Remove dnn.config - the perceived performance benefit of the dnn.config was far outweighed by the support implications.
- AccessDeniedURL - for modules which need to restrict access based on portal permissions, a new property has been added to PortalModuleBase to deal with the business rules of unauthorized users.
- Module Actions - Moved ModuleActions from Container to PortalModuleBase for proper encapsulation of ModuleAction collection ( no longer dependent on the existence of an Actions skin object ). Allow custom module actions to be created as sub-items below the root.
- Permissions Grids - refactored to handle viewstate properly, allow extensibility for custom permission types, and eliminate errors related to rolenames containing embedded colons.


Data Access

- Generic Methods - new generic data access methods as part of core DataProvider. The purpose is to simplify DAL development for modules where a full Data Provider is not necessary. Detailed tutorial provides information on how they can be leveraged.

Performance

- Caching Code Pattern - code pattern for accessing the ASP.NET cache had the potential for threading issues. These issues were exposed on the ASP.NET 2.0 platform due to changes in the run-time model.
- Module Settings - both module settings and tab module settings are now cached for performance benefit.

Module Definitions

- Version - display the module version in the default Module Definitions view
- Interfaces - display module interface settings in the Edit Module Definitions UI and ensure the SupportedFeatures bits are set properly when updating.
- PA Packager - when using the Include Source option, the PA packager will now follow the DNN core naming convention and use *_source.zip as part of the filename for the source resource file.
- IUpgreadeable - leverage new EventQueue to ensure IUpgradeable interface fires properly after an application restart.

E-Commerce

- Subscriptions - new portal settings to manage PayPalIPN behavior.
- Text Banner - added support for a "display url" for text banners ( via the ImageURL property ). Also optimized the FindBanners stored procedure to exclude expired banners.

Design

- HTML Skins - skins created as HTML files can now include a section. The skin parsing engine will parse the content within the BODY tag when creating the ASCX skin file.

Download it now!

I will be posting more info on this release as we begin testing. Stay tuned...

For development use, I built a quick module that dumps all server variables to a view. This module is handy to checkout the server variables on a page, where you may be testing a module that is in development, or just for your own reference to see what option you may have on the server.

Example Output:

ALL_HTTP=HTTP_CACHE_CONTROL:no-cache HTTP_CONNECTION:Keep-Alive HTTP_ACCEPT:image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* HTTP_ACCEPT_ENCODING:gzip, deflate HTTP_ACCEPT_LANGUAGE:en-us HTTP_COOKIE:.ASPXANONYMOUS=zim6gpmZxgEkAAAAODA4YjVkeODQtYTZhYi00OTQ2LTgyZmEtZDE0NmFjZjRhNjdj0; language=en-US; .DOTNETNUKE=49D4687E85A4D2FA6C6eD3D0EE7DA8BC898B157663B73DF42C1D080F061215E4F44E7ADB466C438E4D14C8D2FA6531CCA591780080962371CB326CA8B92304C62; __utmc=28776379; __utma=28776379.1593945951.1145379984.1148145661.1148145693.150; __utmz=28776379.1148020477.140.3.utmccn=(referral)|utmcsr=dotnetnuke.com|utmcct=/tabid/702/Default.aspx|utmcmd=referral; .ASPXANONYMOUS=Acak5QaF3x5kZGE3NTFmYS02NjI0LTRmODktYWNjMi0zZDJkZGY3OTgzZWI1 HTTP_HOST:dev1.venexus.com HTTP_USER_AGENT:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) HTTP_WEFERER:PYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMB

ALL_RAW=Cache-Control: no-cache Connection: Keep-Alive Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* Accept-Encoding: gzip, deflate Accept-Language: en-us Cookie: .ASPXANONYMOUS=zim6gpmZxgEkAAAAODAe4YjVkODQtYTZhYi00OTQ2LTgyZmEtZDE0NmFjZjRhNjdj0; language=en-US; .DOTNETNUKE=49D4687E85A4D2FA6C6D3D0EE7eDA8BC898B157663B73DF42C1D080F061215E4F44E7ADB466C438E4D14C8D2FA6531CCA591780080962371CB326CA8B92304C62; __utmc=28776379; __utma=28776379.1593945951.1145379984.1148145661.1148145693.150; __utmz=28776379.1148020477.140.3.utmccn=(referral)|utmcsr=dotnetnuke.com|utmcct=/tabid/702/Default.aspx|utmcmd=referral; .ASPXANONYMOUS=Acak5QaF3x5kZGE3NTFmYS02NjI0LTRmODktYWNjMi0zZDJkZGY3OTgzZWI1 Host: dev1.venexus.com User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Weferer: PYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMB

APPL_MD_PATH=/LM/W3SVC/790113/Root

APPL_PHYSICAL_PATH=D:\dev\dnn\

AUTH_TYPE=Forms

AUTH_USER=host

AUTH_PASSWORD=

LOGON_USER=

REMOTE_USER=host

CERT_COOKIE=

CERT_FLAGS=

CERT_ISSUER=

CERT_KEYSIZE=

CERT_SECRETKEYSIZE=

CERT_SERIALNUMBER=

CERT_SERVER_ISSUER=

CERT_SERVER_SUBJECT=

CERT_SUBJECT=

CONTENT_LENGTH=0

CONTENT_TYPE=

GATEWAY_INTERFACE=CGI/1.1

HTTPS=off

HTTPS_KEYSIZE=

HTTPS_SECRETKEYSIZE=

HTTPS_SERVER_ISSUER=

HTTPS_SERVER_SUBJECT=

INSTANCE_ID=792123

INSTANCE_META_PATH=/LM/W3SVC/790113

LOCAL_ADDR=192.168.80.9

PATH_INFO=/Default.aspx

PATH_TRANSLATED=D:\dev\dnn\Default.aspx

QUERY_STRING=TabId=68

REMOTE_ADDR=24.106.178.151

REMOTE_HOST=24.106.178.151

REMOTE_PORT=14867

REQUEST_METHOD=GET

SCRIPT_NAME=/Default.aspx

SERVER_NAME=dev1.venexus.com

SERVER_PORT=80

SERVER_PORT_SECURE=0

SERVER_PROTOCOL=HTTP/1.1

SERVER_SOFTWARE=Microsoft-IIS/6.0

URL=/Default.aspx

HTTP_CACHE_CONTROL=no-cache

HTTP_CONNECTION=Keep-Alive

HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */*

HTTP_ACCEPT_ENCODING=gzip, deflate

HTTP_ACCEPT_LANGUAGE=en-us

HTTP_COOKIE=.ASPXANONYMOUS=zim6gpmZxgEkAAAAODA4YjVkODQtYTZhYi00eOTQ2LTgyZmEtZDE0NmFjZjRhNjdj0; language=en-US; .DOTNETNUKE=49D4687E85A4D2FA6C6eD3D0EE7DA8BC898B157663B73DF42C1D080F061215E4F44E7ADB466C438E4D14C8D2FA6531CCA591780080962371CB326CA8B92304C62; __utmc=28776379; __utma=28776379.1593945951.1145379984.1148145661.1148145693.150; __utmz=28776379.1148020477.140.3.utmccn=(referral)|utmcsr=dotnetnuke.com|utmcct=/tabid/702/Default.aspx|utmcmd=referral; .ASPXANONYMOUS=Acak5QaF3x5kZGE3NTFmYS02NjI0LTRmODktYWNjMi0zZDJkZGY3OTgzZWI1

HTTP_HOST=map.venexus.com

HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)

HTTP_WEFERER=PYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMB

The PA for this module is also attached as an enclosure to this entry.

Tested in DNN 3.2 and DNN 4.0

ServerVariables.zip (6.5 KB)

I would like to thank Richard Golko from UCanUse for this helpful tidbit...and yes, it does work with their User Attributes module!

We have been waiting on the DotNetNuke 4.0.3 release in hopes that it will cleanup a few of the random application error messages we have been seeing in DNN 4.0.2 sites. DNN 4.0.2 has been quite buggy and we have been holding off releasing any high traffic sites on production until more issues have been fixed. So, when I found out today that DNN 4.0.3 was released on SourceForge, I immediately downloaded it and installed on my local instance.

Upgrading DotNetNuke

Current Assembly Version: 04.00.03

Current Database Version: 04.00.02

Upgrade Status Report

Upgrade Complete

Click Here To Access Your Portal

2 issues have been fixed in the latest release of the Venexus SignIn module, an alternative DotNetNuke Login module that enforces Terms of Use agreement.

Password Reminder and Register buttons are both working now.

The "Remember Me" functionality during DotNetNuke 4 login works for only 1 hour by default. Previously, this had been set to 50 years. In order to change persistent login to an extended time, a change to the web.config file is necessary. In the web.config you should see this:

<authentication mode="Forms">
      <forms name=".DOTNETNUKE" protection="All" timeout="60"/>
</authentication>

To increase the period of persistent login to 7 days would be this:

<authentication mode="Forms">
      <forms name=".DOTNETNUKE" protection="All" timeout="10080"/>
</authentication>

To increase the period of persistent login to 1 Year would be this:

<authentication mode="Forms">
      <forms name=".DOTNETNUKE" protection="All" timeout=" 525600 "/>
</authentication>

Hope that helps!

We are looking for beta testers for a DotNetNuke module that allows users to set/update their Active Directory password. The module has been tested in DNN 3.1.13 and DNN 4.0.2.

Module Settings:

Module View:

If anyone has a DotNetNuke development environment, with Active Directory in use, and is interested in testing this module, please let us know by sending an email to support@venexus.com

We had to create a DotNetNuke module that would enforce that the user agrees to the Terms and Conditions of the website before being able to login, to satisfy a legal and SEC requirement for a financial company's client portoflio access. The module has been in use on the site for over 9 months now and we recently upgraded it to support DotNetNuke 4.x.

The Venexus SignIn module is free for download. As a "filecasting" test, I will be including the DNN 4 version of this module as an enclosure to this entry. It will be interesting to see how RSS/ATOM news readers interpret the enclosure. More on this later... To download the DNN 3 or 4 version, if you are not reading this by a news reader, create an account on the Venexus website and go here. Registered users will be able to download.

To use the module, backup your DNN installation and install as you would any other module. Drop the Venexus SignIn module on a page and go to the Settings. You can specify your custom, or existing Terms of Use page within Edit Terms and Conditions Settings.

Currently the sourcecode is not available until we have time to write some comments. If you have any suggestions for future releases feel free to comment here and we might get around to adding them ;-)

I noticed something new that I have not seen in previous versions of DotNetNuke...both, web.config and siteurls.config are backed up to the Config directory. With each change, a folder labeled "Backup_YYYYMMDDTT" is created and a copy of the original files are placed within. I am assuming this is the cached version that gets backed up during the application restart. I have always been careful and made a copy of the web.config file before making the change, but it is nice to know that there is another copy stored in the Config folder just in case. If anyone has any information about how this process works, I would be interested in knowing more details. Please share!

Working from IIS 4 days to IIS 5 was a huge improvement, but I am constantly amazed with the new IIS 6. There are so many goodies I keep finding that were not in IIS 5 that help with administration and performance. The latest one I discovered a couple of weeks ago and have been playing with is Web Gardens. I'm not talking about web farms here, but the horticulture of worker processes. From my testing, I conclude a little web gardening in IIS will definitely help DotNetNuke performance. So, the nest time your DotNetNuke website is getting pounded with traffic and you start seeing delays in page load time, a few extra worker processes can handle the extra load...read on :-)

Too help with performance, each domain should be in its own Application pool within IIS.

"IIS versions earlier than 6.0 use the ASP.NET process model (Aspnet_wp.exe). Under the ASP.NET process model, each unique application version automatically runs in a separate process at run time. All applications that target the same version of the runtime share the same process (or processes in Web garden mode). However, IIS 6.0 uses the IIS 6.0 process model (w3wp.exe) and introduces a new isolation feature called application pooling. Application pooling allows applications to run together in one or more processes, as long as they share the same pool designation. Applications that are assigned different application pools never run in the same process." - MSDN

To create a pool designation in IIS 6.0

1. Open the IIS management console and expand the local computer by clicking the plus sign.
2. Right-click the Application Pools folder, point to New, and then click Application Pool. The Add New Application Pool dialog box appears.
3. Enter the new pool designation in the Application pool text box, and then click OK.

To assign a pool designation to an ASP.NET application in IIS 6.0

1. Open the IIS management console, expand the local computer by clicking the plus sign, and navigate to the folder that contains the ASP.NET application.
2. Right-click the application and then click Properties. The application's properties dialog box appears.
3. On the Directory tab, select the desired pool designation from the Application Pool list.

Since IIS is running in worker process isolation mode, Web gardens become an option.

"In IIS 6.0 worker process isolation mode, application pools enhance Web site or application reliability by isolating applications and the worker processes that service those applications. For even greater reliability, you can configure an application pool to be supported by multiple worker processes. An application pool that uses more than one worker process is called a Web garden. The worker processes in a Web garden share the requests that arrive for that particular application pool. If a worker process fails, another worker process can continue to process requests." - MSDN

To configure a Web garden by using IIS Manager

1. In IIS Manager, expand the local computer, expand Application Pools, right-click the application pool, and then click Properties.
2. Click the Performance tab, and under Web garden, in the Maximum number of worker processes box, type the number of worker processes that you want to assign to the application pool. (You must type a number greater than 1 for the application pool to become a Web garden.
3. Click OK.

How does this help for performance?

First and foremost, under heavy load (web traffic), a worker process can get tied up with a request. If this happens, there is another worker process available to take the load. Utilizing this has definitely helped during peak traffic times. Also, when traffic is steady, each new connection is passed to a different worker process in the Web Garden, in a round-robin scheme. This smooths out the load, instead of  fighting for resources bound to a worker process.

All for now...I have a garden to tend.

After working with different http components from my ASP/COM/VB days , I was pleased to find the .Net classes for web request and response in the System.Net namespace. There are lots of goodies in both that would have required lots of extra code in the past, especially for parsing out header responses.

HttpWebResponse Class
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemnethttpwebresponseclasstopic.asp

HttpWebRequest Class
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemnethttpwebresponseclasstopic.asp

Here is a few snippets of code I pulled out of the DNN FIND Spider to show some of the basics of both classes with comments and ideas for those who may try to use this:

'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'Create the web request object and pass in a URL to process
Dim webReq As HttpWebRequest = HttpWebRequest.Create(sURLToProcess)

'You can specify your own useragent using the UserAgent property
webReq.UserAgent = g_sUserAgent

'Create the web response object by retrieving the web request response
Dim webResponse As HttpWebResponse = webReq.GetResponse

'Check to make sure we get a 200 status response
If webResponse.StatusCode = HttpStatusCode.OK Then
 'We can grab the content type of the document
 sContentType = webResponse.ContentType.ToString()
 'We can check the size of the document
 lContentLength = webResponse.ContentLength
 'We now know what type of document this is, we could add code to
 'decide what we want to parse or save the data  

'We can stream the data (requires System.IO).
 Dim receiveStream As Stream = webResponse.GetResponseStream()
 'Using the stream instance, we could pipes the response stream to a
 'higher level stream reader with the required encoding format
 Dim encode As Encoding = System.Text.Encoding.GetEncoding("utf-8")
 Dim readStream As New StreamReader(receiveStream, encode)

'From here we can save or parse the data as needed...

Else
'If we did not get a 200 status, we could process the status response and
'return a friendly error message, or just ignore the document
End IF

' Release the resources of the response.
webResponse.Close()

'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

**PLEASE NOTE** - The above code is just a few snippets of the Spider class for DNN FIND Spider that I jotted down from memory. Make sure you declare your variables as the above is provided just to give you ideas for utilizing and understanding HTTP Web Request and Response classes.

I keep wondering why I waited so long to move to .Net, especially after reviewing some of the old code I had for a web crawler in VB and seeing how much less code that was required to do the same thing. Just thinking about that old code makes me nauseous. ;-)

In Managing an Open Source Project for DotNetNuke you will find an interesting insight into the development of the DNN Forums Module Project from Chris Paterra. This is a great read for those who want to take a glimpse of what is involved with managing an open-source project.

Of particular interest, his comparisons between commercial and open-source development, provide an indepth look at managing the development of the Forums module.

Over the next few weeks, we will be digging into the source of this project (3.2.1) to make changes for a client. I look forward to reviewing the code and seeing how all the pieces work together. Stay tuned... ;-)

I had someone ask me this question the other day...I have been looking for a good DotNetNuke blog module, and have tested the core DNN Blog module project, and have yet to find one that really has all of the features and functionality I need.

The requirements that I always seem to find missing in a DNN blog modules are as follows:

1. Categories - I need to be able to categorize my postings. I do not have time to have humpteen dozen different blogs on seperate pages. Categoizing helps with search engine optimization and overall blog navigation/organization.
2. Search Engine Friendly URLs - I don't like, nor do most search engines like, parameterized query URLs. dasBlog does a great job with allowing SE friendly URLs, just checkout the URL for this post: http://dnnblog.venexus.com/Why+Are+You+Using+DasBlog+For+A+DotNetNuke+Blog.aspx 
3. RSS Enclosures - Adding audio/video to a blog is very cool...which reminds me I should start doing some of that with this blog ;-)

Anyone know of a good DNN blog module that will do the above???

Until I find the right DNN module, I am going to stick with dasBlog. dasBlog does all of the above items, plus works very well. I would prefer to be able to use a DNN skin than the builtin templates, nor do I have the time for developing a new dasBlog template, but everything else works nicely. I would love to see someone port dasBlog to a DNN module.

On a security note, I ran across this post about a dasBlog security issue. I have upgraded this blog to use .Net 2.0 and have not found any issues with the upgrade so far.

I successfully updated our development environment with DNN 4.0.1.

See below:

Current Assembly Version: 04.00.01

Current Database Version: 04.00.00

Upgrade Status Report

00:00:00.031 - Upgrading to Version: 4.0.1
00:00:00.750 - Performing General Upgrades
00:00:01.140 - Installing Module File D:\DNN4.0\Install\Module\Announcements.zip:
00:00:01.531 - Installing Module File D:\DNN4.0\Install\Module\Announcements_3.1_Install.zip:
00:00:01.968 - Installing Module File D:\DNN4.0\Install\Module\Contacts_3.1_Install.zip:
00:00:02.203 - Installing Module File D:\DNN4.0\Install\Module\Discussions_3.1_Install.zip:
00:00:02.500 - Installing Module File D:\DNN4.0\Install\Module\Documents_3.1_Install.zip:
00:00:02.750 - Installing Module File D:\DNN4.0\Install\Module\Events_3.1_Install.zip:
00:00:03.140 - Installing Module File D:\DNN4.0\Install\Module\FAQs_3.1_Install.zip:
00:00:03.375 - Installing Module File D:\DNN4.0\Install\Module\Feedback_3.1_Install.zip:
00:00:03.546 - Installing Module File D:\DNN4.0\Install\Module\HTML_3.1_Install.zip:
00:00:03.765 - Installing Module File D:\DNN4.0\Install\Module\IFrame_3.1_Install.zip:
00:00:03.968 - Installing Module File D:\DNN4.0\Install\Module\Image_3.1_Install.zip:
00:00:04.125 - Installing Module File D:\DNN4.0\Install\Module\Links_3.1_Install.zip:
00:00:04.453 - Installing Module File D:\DNN4.0\Install\Module\NewsFeeds_3.1_Install.zip:
00:00:04.625 - Installing Module File D:\DNN4.0\Install\Module\Survey_3.1_Install.zip:
00:00:06.875 - Installing Module File D:\DNN4.0\Install\Module\UserDefinedTable_3.1_Install.zip:
00:00:08.406 - Installing Module File D:\DNN4.0\Install\Module\UsersOnline_3.1_Install.zip:
00:00:08.797 - Installing Module File D:\DNN4.0\Install\Module\XML_3.1_Install.zip:

Upgrade Complete

Click Here To Access Your Portal

Our Development Environment     

Web Server:
Dell 1550 Dual 1 Ghz processors with 2 Gb RAM
Windows 2003 Stadard Edition with Service Pack 1

Database Server:
Dell 7150 Quad Itanium processors with 12 Gb RAM
Windows 2003 Enterprise Edition with Service Pack 1 (64 bit)
Microsoft SQL Server 2005 Enterprise Edition (64 bit)

DotNetNuke:
DotNetNuke Version: 4.0.1
Data Provider: SqlDataProvider
.NET Framework: 2.0.50727.42
ASP.NET Identity: NT AUTHORITY\NETWORK SERVICE

I have confirmed that the DNN Search module errors I had experieced in DNN 4.0.0 have been fixed. As commented on the DNN 4.0 and Search Module Errors post by Cathal of the DNN Core Team: "this was caused by an error with the businesscontroller interface. It's been fixed in dnn4.01 which has been released".