• Complete OOP Support - O/SP Mapper supports inheritance and polymorphism with all .NET collection functionality fully implemented via .NET Generics.

• XSD Schema/XML Support - Complex types, extensions, includes. Also included is the ModivateXSDGen library, a customized version of the Microsoft XSD Class Generator specifically tailored for generating domain objects for O/SP Mapper. Developers can create their domain model in XSD schemas and have the O/SP Mapper domain objects generated automatically.

• Full Developer Transaction Control - Transactions to the database can be committed at a single object, collection or recursive object hierarchy level as well as purposefully leaving transactions open across multiple calls to the O/SP Mapper Persist methods on different objects.

• O/SP Mapper XML Configuration File - An XML configuration file is used to enforce your own .NET and database naming standards to identify key elements required by O/SP Mapper. These include domain object namespaces, stored procedure naming conventions, base Generics IList implementation name, base domain object name, critical domain object property names (ID, Name, Audit Properties, etc.), CRUD .NET and SP naming conventions and specialized domain object traversing method naming conventions.

• Optional Domain Object Persistence Features - If your database tables are designed to Modivate's recommendations, O/SP Mapper provides functionality to support logical vs. physical record deletes, record audit trail management, automated dirty object event notification and persistence as well as historical "Point-In-Time" data management and recall.

• Object Hydration Level Flexibility - On any call to hydrate or persist an object with 0-to-n levels of child object properties and collections, a developer can indicate the number of levels down the hierarchy to hydrate or persist the object members. The default is "unlimited" object hierarchy hydration. This provides an environment for full control of lazy-loading as the developer desires.

• Zero .NET Reflection Used In O/SP Mapper - The great performance killer for almost all O/R mapping tools is avoided in O/SP Mapper via dynamic emitting lightweight .NET IL (Intermediate Language) assemblies cached in the .NET worker process to manage Get and Set operations.

• IModivateDataProvider Plug-In Option - If we don't support the database that you want to use, you can implement your own data provider based upon the IModivateDataProvider interface provided.

• XML O/SP Mapping File - This file allows the developer to:
  • Map object properties to stored procedure parameter and return values
  • Map .NET methods to stored procedures
  • Map child property object hydration paths manually to stored procedures other than the basic CRUD Read procedure.
  • Map child object properties at the same level as the parent object. This provides a mechanism to make one call to a stored procedure to populate a multi-level hierarchy based object or collection of objects. In the called stored procedure, you could then make SQL joins to other tables to de-normalize the data that will in return perform faster and result in fewer calls to the database.

Modivate strives to continuously make sure O/SP Mapper is feature-rich, performance focused, data architecture standard driven and professionally supported.