Depends :) It's down to NH, not FNH really. NH takes quite a while to validate what we give it. Do your unit tests need the entire domain? If not you could build a separate PersistenceModel instance with just the classes you need in.
In our model branch (which will become 1.0 in the not-too-distant future) we've implemented merging of mappings, which speeds up BuildConfiguration when there's a lot of mappings. On Thu, Jul 23, 2009 at 11:07 AM, Mikael Henriksson <mik...@zoolutions.se>wrote: > Is it possible to tweak the configuration part for performance somehow? Now > that the number of classes increased unit testing has become a bitch. It > takes forever to do .BuildConfiguration(). Is there something I can do to > improve this time? When it's deployed I don't give a rats ass but while I > run my tests etc it has become sort of annoying! > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
