you *can* tweak your build process to chunk all of the hbms into a single
one, based on DEBUG/RELEASE

Anyway, afaik the problem is with XML validation (that is probably happening
per-file when you have more than a single one).

so - it may be better off caching the compiled config.

how?  you create the config regularly, then you serialize the cfg into a
file. deploy that file to PROD and deserialize it back.

look here:
http://nhforge.org/blogs/nhibernate/archive/2009/03/13/an-improvement-on-sessionfactory-initialization.aspx



another option - use FluentNhibernate for configuration. it need not XML
validation, thus is should be way faster to initialise.




On Sat, Jun 13, 2009 at 3:24 PM, antoschka <[email protected]> wrote:

>
> I did some searching to the topic mentioned above.
>
> It seems that using one hbm file instead of separate ones solves a lot
> of problems. However I would like to go on having separate files
> during development - how could I achieve a merging to one hbm file
> each time I build my solution and make it as an embedded resource?
>
> What else can I do to improve startup time??
>
> Thanks for your help
>
> antoschka
> >
>


-- 
Ken Egozi.
http://www.kenegozi.com/blog
http://www.delver.com
http://www.musicglue.com
http://www.castleproject.org
http://www.gotfriends.co.il

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to