Hi,

During development of my first orchard module (area, not a content type or widget) I've updated the content of migrations.cs file without upgrading the version (don't see the need before something is released).

To force migrations to occur again, I removed the table from my SQL Server database and deleted the record in table 'Orchard_Framework_DataMigrationRecord'.

The migrations.cs file runs and the updated version of my table is created.

However, NHibernate seems to recognize only the fields that were present in the first version of migrations.cs.

How does the mapping work? I assume it is cached somewhere?

mappings.bin in your site folder under app_data.

Yes, I saw this file was mentioned in the docs. I renamed it to see if it changed anything, but it didn't (didn't get rebuilt nor did NHibernate act differently).

Do I need to delete this file and run migrations.cs again to get it rebuilt?

Did you restart the webserver? It does recreate for me if I remove it.

I didn't. I will try this later today.

Thanks, both!

Mappings are generated at startup based on enabled modules. The mappings are cached in mappings.bin, and a checksum is generated. Altering a record or a module will change this checksum and regenerate this file/mapping.

Yes, it's working.

I removed my table, removed its record in table 'Orchard_Framework_DataMigrationRecord', deleted mappings.bin and restarted IIS.

When starting up Orchard, migrations.cs ran and mappings.bin was recreated. And sure enough, NHibernate now works with all fields!

Thanks, all!

Worked for me too! Happy days! :-)