I started playing with Orchard and created a custom module. I installed it on a test server we were using. People have created content on the test server using the original module. Later, I fixed up the module and cleaned up the namespaces it uses. (of
course you all know what is coming next...)
Now I want to deploy the updated and improved version of the module which has a different namespace. My questions are "what is going to break? and how do I fix it?"
I know that the table Orchard_Framework_DataMigrationRecord uses the namespace in the fully qualified class name that is stored in DataMigratonClass to track data migration versions. I know how to fix that. Is there anything else that may break if I update
a module and the updated version uses different namespaces?