Guys, what do you think about the concentration on creation
of xml mapping files in development of application based on NHibernate.
The idea is that the main role play NHiberante mapping files.
All other stuff: CSharp entity classes and database scheme
scripts should be created automatically from mapping files.
So the magic tool or library could provide:
1) generation of cs files
2) automated creation of .net assembly
3) generation of database creation scripts (including tables and constraints
)
4) generation of indexes to the database for foreign keys in collections
5) generation of alter table script in case of xml mapping changes
( the script could use previos and new versions of xml-files or the combination: new version of xml-files and current db-scheme)

These could help to create more dynamically applications based on NHibernate. The application could change the data model on-the-fly
and link with with NHibernate DAO not statically but via reflection.

I plan to use this approach to create adaptive information-analytical system.[/b]

I assume you are talking about a tool using available tools...

1) hbm2net
2) NAnt
3) hbm2ddl
4) hbm2ddl ?!?
5) SchemaUpdate (not available)

On side note, I really prefer writing cs files and use NHibernate.Mapping.Attributes to generated the hbms and database scripts :wink:

Hi KPixel.. can you provide example code how to generate hbm.xml file and database schema from *.cs file..

or any example in NHibernate Project Solution..

Both the NHibernate.Mapping.Attributes tool and Castle's ActiveRecord generate the xml mapping for you. The unit tests for each should provide examples of generating the database schema. See http://svn.castleproject.org/svn/castle/trunk/ActiveRecord/Castle.ActiveRecord.Tests/AbstractActiveRecordTest.cs to see how ActiveRecord does it.