An EF provider potentially now provides four services:
DbProviderServices -- main EF provider
DbSpatialServices -- spatial services; obtained from main provider or registered globally
MigrationSqlGenerator -- SQL gen for migrations; registered per invariant; can be overridden in migrations config
IHistoryContextFactory -- registered per migrations context type or as default
It would make it easier for provider writers if they could register one thing in the config file (say just DbProviderServices) and it would resolve all the other services as dependencies. (This would have to exclude the global spatial provider.)
Comments: Make sure to consider this item: http://entityframework.codeplex.com/workitem/536
DbProviderServices -- main EF provider
DbSpatialServices -- spatial services; obtained from main provider or registered globally
MigrationSqlGenerator -- SQL gen for migrations; registered per invariant; can be overridden in migrations config
IHistoryContextFactory -- registered per migrations context type or as default
It would make it easier for provider writers if they could register one thing in the config file (say just DbProviderServices) and it would resolve all the other services as dependencies. (This would have to exclude the global spatial provider.)
Comments: Make sure to consider this item: http://entityframework.codeplex.com/workitem/536