Wrox Programmer Forums
|
BOOK: Professional DotNetNuke Module Programming ISBN: 978-0-470-17116-5
This is the forum to discuss the Wrox book Professional DotNetNuke Module Programming by Mitchel Sellers and Shaun Walker - Wrox DotNetNuke Series Editor; ISBN: 978-0-470-17116-5
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional DotNetNuke Module Programming ISBN: 978-0-470-17116-5 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old April 1st, 2010, 11:56 AM
Authorized User
 
Join Date: Jan 2010
Posts: 29
Thanks: 0
Thanked 1 Time in 1 Post
Default IUpgradeable Implementation

I got this working and wanted to share the process, as there is a key portion missing in the textbook.

Expanding on the DNN Manifest options on pages 277 & 278:

To trigger DNN into running iUpgradeable code in the BusinessControllerClass, it's necessary to add another section to the manifest. Look inside of the <Component type="Module"><Component> element. Right after closing the <desktopModule></desktopModule> section, add a node for <eventMessage></eventMessage>.

Here is an example:

Code:

<eventMessage>
	<processorType>DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke</processorType>
	<processorCommand>UpgradeModule</processorCommand>
	<attributes>
		<businessControllerClass>CD_Development.Modules.CD_Announcements.CD_AnnouncementsController</businessControllerClass>
		<desktopModuleID>[DESKTOPMODULEID]</desktopModuleID>
		<upgradeVersionsList>01.00.00,01.00.01</upgradeVersionsList>
	</attributes>
</eventMessage>
You can copy and paste most of this. Make sure to substitute your own <businessControllerClass> value.

The <upgradeVersionsList> is where you trigger each section of your iUpgradeable code (inside your BusinessContollerClass). Refer to pages 165 & 166. It's perfectly ok to run more than one 'version' code section (meaning you can run the code for multiple versions like 01.00.00, 01.00.01, etc). You aren't restricted to running the upgrade code for only the current version. In my specific case, I need to add a scheduler item to the DNN Scheduler - doesn't matter what version my module is. So I have this coded in my 'Case "01.00.00"...' section. I didn't have to bother changing anything in my BusinessControllerClass, even though my module is now a higher version. To do this, add multiple version numbers inside of the <upgradeVersionsList></upgradeVersionsList> element and seperate each with a comma. Do not use quotes around the values, and don't add a space.

Example:

<upgradeVersionsList>01.00.00,01.00.01</upgradeVersionsList>





Similar Threads
Thread Thread Starter Forum Replies Last Post
jms implementation yanis97 J2EE 0 August 31st, 2006 04:29 AM
pagination implementation vivekkumar_23 Struts 1 July 12th, 2006 05:52 AM
IComparer implementation Bob Bedell C# 1 February 6th, 2006 02:28 AM
COM Implementation using VB6 haianoop Pro VB 6 0 December 28th, 2005 04:01 PM
c# implementation help cshanmuganathan ASP.NET 1.0 and 1.1 Basics 1 May 28th, 2005 12:08 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.