Hi Abhishek,

After you have added your new module definition, you need to package and install the module on your DNN installation in the normal way. When you add the module to a page in your portal, each of the definitions in your module will be inserted on the page. You can then move them to different pages, as needed.

However, I think I may have only partially answered your question. If you mean what happens to the controls from the previous version of the module already on the page, that's a very good question. Unless anyone else can cast more light on this, I suggest you try it out on a test installation, and see what happens. Have a look at the ModuleDefinition table before and after installing the new version, and check to see if the definitions in the new version update existing ones, or are newly created. Do old definitions get deleted, or do they remain in the table? Also, have a look at the pages where you had your module installed, and see the result.

Your strategy for updating will depend to some extent on whether you need to retain module data during the upgrade. If you are able to simply delete old module instances and replace them with the new version, the task is simple. On the other hand, if you need to retain the data, and the data has a relationship to the ModuleID, I think you'll need to find a way of migrating it. In the worst case, if your module supports IPortable (ie. Import / Export), you could use this as way of doing the migration.

---

Paul Taylor

DotNetNuke, ASP.NET and SQL Server Development