I tried this and it helps. There was a problem where it wasn't able to find the DLL correctly when checking dependencies because it uses just the name from the config. But the DLLs were in some common folder for some reason when I was debugging. I modified the code to load the assembly and get the name and then it works.
Now, is there anything I can do to speed up Windsor? Thanks. On Fri, Apr 17, 2009 at 12:18 PM, Tuna Toksoz <[email protected]> wrote: > Or better (most of the time) > > > http://nhforge.org/blogs/nhibernate/archive/2009/03/13/an-improvement-on-sessionfactory-initialization.aspx > > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksoz > http://tunatoksoz.com > http://twitter.com/tehlike > > > > > On Fri, Apr 17, 2009 at 7:14 PM, Mauricio Scheffer < > [email protected]> wrote: > >> >> If, after profiling, you see that NHibernate is taking the most time, >> see: >> >> >> http://ayende.com/Blog/archive/2007/10/26/Real-World-NHibernate-Reducing-startup-times-for-large-amount-of.aspx >> >> On Apr 17, 11:20 am, crimsondr <[email protected]> wrote: >> > Hi all, >> > >> > I use monorail with windsor and nhibernate. I have many services and >> > many model classes which makes both windsor and nhibernate take a long >> > time to start up. >> > >> > Are there any general hints or tips that I can do to help make the >> > start up faster? >> > >> > Thanks. >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
