I'm noticing that the DataProviderBase has method signatures that include IDataItem. IDataItem includes a property for Id that is a Guid.
Our dba's get their panties in a bunch when we talk about guid's as primary keys, even with the newsequentialid functionality.
Is there any way to use integers as primary keys in 4.0 without totally bypassing the built-in base classes?
I'm continually amazed at the quickness of the customer support that you provide.
Let me ask one follow up question.
Does "Custom implementation" mean that we could implement all the nice juicy base classes but ignore the id property on all our model classes? Or would a Guid.Empty id blow stuff up? We are not using OpenAccess, but rather entity framework, so I'm not concerned with the provider implementation - but the related stuff like the module, manager, and ui stuff like ViewModeControl<T>, etc.