I'm packaging an upgrade to a rather complex module I wrote 6 months ago. The original 04.00.00 version included an xml file (placed in the module's App_LocalResources folder) containing some 30 e-mail templates. I don't want to include this xml file (which hasn't changed) in the module 04.01.00 upgrade package out of concern that it will overwrite the templates which a user may have customized since the original install. If I don't include it in the upgrade package then anyone doing a new install rather than an upgrade from the 04.01.00 package will not have this essential file available.

How have other's handled inclusion of such files in an upgrade package? I can see three alternatives: 1)  Include the template file but advise users that are upgrading to temporarily rename their modified template file then copy it back over the new, unmodified file; 2) Include the template file with a different name then implement using the IUpgradable interface an automatic rename of the new template file to its correct name if one does not exist from a previous install; or 3) Not include the template file in the module upgrade package but make it available as a separate file for new installations only. I'm leaning to #2, but would like to have some other opinions.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Thanks Sebastian - That's what I decided to do, implementing it as part of the IUpgradable.UpgradeModule method. It seems to work well, though I had a tough time getting the absolute path to the files. It seems that use of HttpContext.Current.Server.MapPath when used in the UpgradeModule kept adding in virtual folders from a previously accessed tab, resulting in something like:

C:\DNN4Test\Admin\LogViewer\tabid\48\DesktopModules\ . . . rather than C:\DNN4Test\DesktopModules\ . . .

I suspect that the current context is not valid while UpgradeModule is running. I finally used the following to build my absolute path:

DestFilepath = DotNetNuke.Common.Globals.ApplicationMapPath & "\DesktopModules\" & _
                 dmi.FolderName & "\" & Localization.LocalResourceDirectory & "\Templates\EMail.xml"

where dmi is my DesktopModuleInfo object. Hope this helps someone trying to do a similar operation in their UpgradeModule method

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner