@fabio +1 @Huge, what you are asking for is NH without NH. It like asking for a car, with no wheels and no engine.
On Aug 3, 9:34 pm, Fabio Maulo <[email protected]> wrote: > You don't need NHibernate. What you are looking for is Linq2Sql. > > -- > Fabio Maulo > > El 03/08/2010, a las 19:19, Huge <[email protected]> escribió: > > > Greetings, > > I was wondering if it would be possible to make available a so-called > > "Lite" build of NHibernate. NHibernate seems to have a lot of > > features that I do not want or need, and I'm concerned about the >2MB > > download size. > > > Lazy Initialization: this is the one I would most love to get rid of. > > Yes I have read hundreds of posts singing the praises of why Lazy > > Initialization is so great. Well my particular app cannot benefit > > from Lazy Initialization at all. I want to completely disable this > > feature. It seems to me that there should be a global place in the > > Config where you can disable Lazy Initialization. > > > FYI the guidance on using a short-lived ISession and the seemingly > > forced usage of the Lazy Load feature seems in direct contradiction to > > me. On the one hand it is recommended to use a short-lived ISession. > > Well if it is short lived and my collections are not loaded as I wish, > > then when I do get around to accessing those collections I always get > > a nasty LazyInitializationException. Can't I just turn of Lazy > > Loading in a global Config setting, pretty please? > > > When you download NHibernate there are the 2 folders: required_bins > > and required_for_lazy_loading which has the Castle and Linfu DLLs. > > What if I don't want to use Lazy Loading AT ALL? How can I run > > NHibernate without a dependency on these Proxies? This should be an > > available option! I'm forced to choose one of the Bytecode providers > > or NHibernate won't run. > > > Sure log4net is great but it doesn't belong in our production app! We > > already have a legacy logger that cannot be replaced. So I need an > > option to not have a reference to log4net. Why isn't this a compile > > switch or something? All this baggage! > > > I'm writing a Windows WPF desktop app that interfaces with MSSQL > > Server. So why do I now have a reference to System.Data.OracleClient > > and System.Web after linking to NHibernate? These extra DLLs really > > bloat my project and I need a compile option to get rid of the extra > > stuff I don't need. My users must download my app and now it grew by > >> 2MB because of a bunch of stuff I don't need that's tacked onto > > NHibernate. > > > ...in short, a LITE build of NHibernate. > > > I have done a couple things towards making my own compile of > > NHibernate without the OracleClient references. I'm just really > > baffled that NHibernate is such a widely used ORM but has these extra > > dependencies built in and required. > > > I should be able to use NHibernate in a stripped down form to just > > give me the basic ORM functionality I need without all this extra > > baggage. > > > Thank you for listening. > > Hugh > > > -- > > 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 > > athttp://groups.google.com/group/nhusers?hl=en. -- 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.
