I'm +1 for this. With the active assembly partitioning being done at ms, more and more we need to be careful on dependencies taken.. Castle.Core, as the name implies, should have minimal dependencies.
On Fri, Sep 10, 2010 at 6:36 PM, Jonathon Rossi <[email protected]> wrote: > So that's 4x +0's so far which I think in true ASF terms doesn't give you an > answer. > > +1 from me, I don't use the WebLogger and I doubt many people do. Lets just > make things easier for all users of DP on the client profile, including > NHibernate, RhinoMocks, Moq, etc. > > You'll also need to remove the #ifdef for CLIENTPROFILE in the WebLogger > class if you haven't already, so that we'll get the class and the logging > facility won't break. > > On Sat, Sep 11, 2010 at 11:19 AM, Patrick Earl <[email protected]> wrote: >> >> The main NHibernate assembly on the trunk works fine with the client >> profile. The current issue is with the castle bytecode provider in >> NHibernate. I'm not aware of any plans to do a dual release for >> client / full. Without further intervention, I believe what was going >> to happen was that they would release with the full Castle.Core >> assembly and leave people to figure out their own client profile >> support. >> >> If Castle.Core adopts client profile support, then NHibernate could >> upgrade to 2.5.1 and then both full and client profile users could use >> the single distribution with no changes. >> >> To be clear on my level of knowledge, I'm not a committer for >> NHibernate, just an active patcher. ;) >> >> Patrick Earl >> >> On Fri, Sep 10, 2010 at 6:42 PM, John Simons <[email protected]> >> wrote: >> > +0 >> > >> > But still confused! So is NHibernate vNext going to release a CP and >> > full or just CP? >> > >> > Cheers, John >> > >> > On 11/09/2010, at 3:38, Patrick Earl <[email protected]> wrote: >> > >> >> Yes, only the WebLogger. >> >> >> >> 2010/9/10 Henry Conceição <[email protected]>: >> >>> It's only the WebLogger right? >> >> >> >> -- >> >> 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. >> > >> > >> >> -- >> 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. >> > > > > -- > Jono > > -- > 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. > -- Cheers, hammett http://hammett.castleproject.org/ -- 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.
