Ricardo; imho forcing that reference being a problem is a straw-man. We're already referencing so many things in web applications that another one doesn't matter that much.
However, sometimes you are correct - then perhaps there could be a registration API where you choose which references to take, such that C.F.NHib is the 'core' and C.F.NHib.Fluent is the one tying it together with fluent, for example. The registration API - yes, that could be improved; it could probably be easily ported from the other facility. So the question remains; what would you like to do guys? :) Cheers, Henrik From: [email protected] [mailto:[email protected]] On Behalf Of Ricardo Borges Sent: den 1 augusti 2011 14:30 To: [email protected] Subject: Re: NHibernate Facilities Henrik, Well done with the facility, it is really more lightweight... but, the another facility has some important flexibilities (IMHO), as the IConfigurationBuilder... what if I don't want to map with FluentNHibernate? Fluent is just one of them... I would prefer to not force that reference and usage. 2011/8/1 Henrik Feldt <[email protected]> Well, the two facilities is just because of me. The other one works excellent for what it is intended for... I'd happily rename mine if that's wanted, to something that doesn't conflict, but that's why I started this thread on the devel list. I want to know what people think... If we make a decision we can then show a unified front instead. ^^ Another option could be to merge them and release a new major of NHibernateIntegration, while still having the alias C.F.NHibernate (so that both work). Cheers -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of dagda1 Sent: den 1 augusti 2011 11:03 To: Castle Project Development List Subject: Re: NHibernate Facilities As a long term Castle user, following castle can be frustrating. I love your work and use loads. <The next passage is tongue in cheek and not meant to be rude> I find the way the project is ran mystifying at times. First of all you split everything up into individual projects and then you gradually start bringing them all together. Now you want to give us 2 very similar Nhibernate facilities (already I don't know what to call it). Surely you realise that this causes complete confusion for a user for which one to use? I don't think castle will ever be in a state where it is not moving back and forward from one state to the next. With horn it was the castle dependencies that caused a lot of the mayhem. Every OSS project had a different version of Caslte.Core. Please take this criticism lightly and tongue in cheek but it does have a serious note. I love your stuff. I hate the way things are in a constant state of flux. P.S. I was in charge of the Horn project (R.I.P.) and look how well that went :-) On Jul 31, 9:03 pm, Ricardo Borges <[email protected]> wrote: > I've used NHIntegration in several projects... I released one last week! > Always successfully, web and desktop apps > > 2011/7/31 Henrik Feldt <[email protected]> > > > > > > > > > > > Hello everyone,**** > > > ** ** > > > What do you think ofhttps://github.com/haf/Castle.Facilities.NHibernate? > > **** > > > ** ** > > > I created it because I felt the other NHibernateIntegration was > > getting too large and unwieldy. This facility is working well for my > > projects and some people are starting to use it.**** > > > ** ** > > > Should we retire NHibernateIntegration in favor of this facility or > > should we do something else with them?**** > > > ** ** > > > Regards,**** > > > Henrik **** > > > ** ** > > > -- > > You received this message because you are subscribed to the Google > > Groups "Castle Project Development List" group. > > To post to this group, send email to > > [email protected] > > . > > To unsubscribe from this group, send email to > > [email protected] <mailto:castle-project-devel%[email protected]> . > > For more options, visit this group at > >http://groups.google.com/group/castle-project-devel?hl=en. > > -- > Ricardo -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:castle-project-devel%[email protected]> . For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:castle-project-devel%[email protected]> . For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- Ricardo -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.
