I built a Module whose Business Controller Class did NOT implement IUpgradable in the first version (01.00.00).

The Module then went through a series of incremental upgrades. I recently finished work on a major upgrade to the Module with breaking changes from older versions.

The installation of this upgrade required performing some actions that lay outsie the normal DNN Upgrade process (DataProvider files, clean-up txt files) etc.

So, I implemented IUpgardable on the BusinessControllerClass in this version. However, to my surprise, when I uploaded the new version into a test DNN install, no Upgrade logic was executed. I checked the Module Definition, and there was NO check mark in front of the IUpgradeble module capability.

So, does that mean that if a BusinessControllerClass does not implement IUpgradable in the first version, no later version could do so?? Is there any way of getting the Upgrade logic of this new version executed during the install process???

Thanx for the reply. The Module was originally built against 4.8.2 and now running on 4.9.0.

And I double checked your checklist, and I was doing everything right. So, I later decided to dig deeper into the core onto what happens when a module is installed and how does the core checks which interfaces are implemented.

I found that the core creates through Reflection an object of the specified BusinessController Class, and checks the object for implemented interfaces. And trying to create an object of my BusinessController class was throwing an exception.

And there, I had it. My Controller did NOT had a parameterless constructor. It had a Parameterized constructor only. And that was where the problem lied.

So, I added a parameterless constructor, and voila, everything was back to normal.

As a passby, I would suggest the Code team NOT to catch & ignore the execption generated trying to create an object of the Controller class during Module installs and upgrades, but add an Event entry for it. Creating object via Reflection might fail due to a variety of reasons, and creating a Log Entry would help the developer to determine what exactly went wrong.