The CodeSmith templates for the Wilson ORMapper have been updated. There are many great new features. Most of the new features are for .net 2.0. The following is a summary of the new features.
The mapping file in now updated. Only the settings that need to be updated from the database are changed. Settings like sortOrder, readOnly, lazyLoad, and many others can be edited manually and not be overwritten when the template re-runs. You can also manually add entity elements and not have it changed by adding an attribute ‘generated’. <entity … generated="false">
Major overhaul to the class generator
- Classes now inherit from a bass class called PersistBase<T> or RetrieveBase<T> for readonly entities. The base classes contain most of the functionality and make it easier to make API changes.
- Classes now have full support for ObjectDataSource binding. ObjectDataSource can be tricky to use. There will be a tutorial in the future on how to use the templates.
- Classes support validation with the addition of the IsVaild method.
- Classes now track IsDirty and IsDeleted.
- Simplified the API by creating more overloads. Renamed several functions, like RetrieveScalar to RetrieveFirst.
- Generator now supports the lookup element of the mapping file.
- Added a TransactionManager class to make working with transactions easier
- The class generator can now update a project file with the generated files. Generated partial classes are now hidden under the standard class, like the Windows Form designer files. The mapping file is also added to the project and marked as an embedded resource.