Those people who like to do their mappings via the custom attributes (AFTable etc) at the moment still need to have an XML file to define the database mapping.
I should be able to create an assembly level custom attribute for the database mappings (AFDatabase or something) that can be put in AssemblyInfo.vb and then they don't need an AtomsFramework.XML file at all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since I'm going to start work on 2.1 soon I've branched v2.0 in CVS (for both dotnet and the nunit tests)
The main aims for 2.1 are
1. Move database providers to separate .dlls to simplify distribution when some providers are not needed or available.
2. Try to enable XML free usage (ie move the database setup into attributes)
3. See if we can't do something about referential integrity/foreign keys
4. Try to simplify many-to-many associations
- Richard.
Hi Richard,
Regarding point no. 2, what does it mean?
XML free usage?
Those people who like to do their mappings via the custom attributes (AFTable etc) at the moment still need to have an XML file to define the database mapping.
I should be able to create an assembly level custom attribute for the database mappings (AFDatabase or something) that can be put in AssemblyInfo.vb and then they don't need an AtomsFramework.XML file at all.