Is there a reason that DataObjectTypeName is used to establish the meta model? It's kind of annoying being bound to setting the DataObjectTypeName on the parent ODS in order for the Dynamic version to work.
I added a "DynamicDataTypeName" to the DynamicODS which works out nicely cause now I can still use all our Business logic (which do not take instances of the object... which is what I prefer most of the time)
Also by not being bound to setting DataObjectTypeName, I can set the type used for the Meta data to an interface or an abstract base class.. Which is also very convenient
All I did in code was add a DynamicDataTypeName property and change the line which establishes the DataObjectType
PureWeen
Participant
1221 Points
317 Posts
recommend using DynamicDataTypeName instead of DataObjectTypeName on DynamicObjectDataSource
Sep 02, 2008 07:47 PM|LINK
Or MetaTypeName......
Is there a reason that DataObjectTypeName is used to establish the meta model? It's kind of annoying being bound to setting the DataObjectTypeName on the parent ODS in order for the Dynamic version to work.
I added a "DynamicDataTypeName" to the DynamicODS which works out nicely cause now I can still use all our Business logic (which do not take instances of the object... which is what I prefer most of the time)
Also by not being bound to setting DataObjectTypeName, I can set the type used for the Meta data to an interface or an abstract base class.. Which is also very convenient
All I did in code was add a DynamicDataTypeName property and change the line which establishes the DataObjectType
DataObjectType = BuildManager.GetType(DynamicDataTypeName, true);
Is there something I'm missing?
Some impossible hurtle I'll encounter by having done this?