In creating a new version of a module, I changed the name of the .ascx files, so now when I perform an upgrade, I am left with two .ascx references to the same key. The old .ascx and the new .ascx  I was hoping the upgrade would update the .ascx file in the existing database record as all other information is the same.  But this seems not to be the case.    The view seems to work (not sure why), but accessing any edit modules causes an error that more than one .ascx is defined and that there must only be one.

I have deleted the old .ascx file from the \desktopmodule directory via the xx.xx.xx.TXT file.  (small issue:  Is there any logging of the deleted files in the update log?)

How do I delete the old reference from the database?   I am testing with DNN 4.5.5 as this will be oldest version I want to support with the new version.   I could delete the old reference via  SQL during the upgrade - but is this the recommended way?  What is the best practice in this case?

Any help would be appreciated.

Thanks
Paul

Bill, Thanks for the suggestion. The IUpgradable interface code will basically perform the SQL Update I was suggesting. However, using the controllers will ensure I don't damage the underlying database structures. I will look at doing this, but I thought the manifest file would handle it... Time to launch VS and add the required code. I will post an example for others like me that we looking for a solution via the manifest file. Can you suggest one of the "older core modules " to review? Thanks, Paul.

Thanks for the feedback.  /Paul