Hi cincura_net,
Your approach with the command tree is not horrible and is probably the best you can do right now.
Another thing to consider would be to provide a custom impl. of HistoryContext. This is the hook we added to allow providers to customize the history table model via a more standard OnModelCreating approach. Users need to register your custom history context type in their Migrations configuration.
Cheers,
Andrew.
Your approach with the command tree is not horrible and is probably the best you can do right now.
Another thing to consider would be to provide a custom impl. of HistoryContext. This is the hook we added to allow providers to customize the history table model via a more standard OnModelCreating approach. Users need to register your custom history context type in their Migrations configuration.
Cheers,
Andrew.