I would like to see client profile support in NHibernate. Just as a data point, the castle project has already started to embrace the client profile.
Microsoft is pushing client profile pretty hard. The VS2010 Console Application wizard defaults to client profile. I believe Windows Update defaults to providing the client profile for .NET 4.0. The client profile is good for developers and makes deployment of the .NET framework smaller and easier. -Michael Maddox http://www.AgilityForORMs.com/Home/Products On Mon, Aug 2, 2010 at 6:01 AM, Craig van Nieuwkerk <[email protected]> wrote: > I think client profile will become much more important in the future. > It is only just becoming used frequently with .NET 4 and I suspect > most desktop applications will soon prefer it. If the work required > doesn't require major rewriting I would say go for it, especially if > Patrick is happy to do most of the leg work. > > Craig. > > On Mon, Aug 2, 2010 at 8:56 PM, Fabio Maulo <[email protected]> wrote: >> Patrick, >> Are you sure that the client-profile-support is so fundamental ? >> So far you are the only one talking about it. >> Before begin a big work in NH-3 I would be sure about how much important is >> the client-profile-support for NH future. >> >> On Mon, Aug 2, 2010 at 6:34 AM, Patrick Earl <[email protected]> wrote: >>> >>> For myself, I'm not particularly opinionated in any direction other >>> than the direction that will allow for client profile support. If >>> this happens through a custom pluggable logging layer, common.logging, >>> or some other way, I'm happy. It seems like the common.logging >>> library is a good fit, but it's not already on the trunk so I'd be >>> curious to know why. >>> >>> The last log4net release was in 2006 and the mailing list is pretty >>> quiet in terms of "getting it done" type traffic. It also seems like >>> over time there has been not insignificant demand for the ability to >>> use a different logging framework. Using something like >>> Common.Logging seems like a good way to solve the problems with the >>> client profile dependencies and the different logging framework >>> support. >>> >>> I don't think that replacing log4net with Common.Logging is like >>> trading one "evil" for another. Common.Logging has a much smaller >>> footprint than the actual logging frameworks and was designed to solve >>> the pluggable logger problem. If this is what is desired for >>> NHibernate, why not utilize the work of others? On top of this, there >>> is already a patch to implement this change in NHibernate. >>> >>> I'd very much like to have this issue pushed to completion. If it >>> involves additional development, testing, or documentation time, I >>> would be happy to volunteer my time. I just need to know where to put >>> my energy. >>> >>> Patrick Earl >> >> >> -- >> Fabio Maulo >> >> >
