Data Migrations don't run when module folder name not the same as module project name

Topics: Writing modules
Jun 23, 2011 at 1:18 PM

It took me forever to figure this out. It all worked fine on my dev machine, but when I deployed it to my production machine I renamed the folder the module was in. The module feature would show up fine in the features list, but when enabled it never ran the migrations. I didn't see if it messed with any other aspects of the module.

When I finally renamed my module folder the same as its contained project, Orchard alerted me the module was due for an update and ran the migrations.