Hi Guys,

First of all, I am a big fan of Castle and use many parts of the
stack.  Please see this as not a criticism but feedback.

I am writing this to see if there is anything that can be done to
alleviate what I and others are going through when it comes to
updating a stack that heavily uses castle.

I use:

Castle.Core
Castle.Components.Validator
Castle.DynamicProxy2
Castle.Facilities.AutomaticTransactionManagement
Castle.Facilities.NHibernateIntegration
Castle.Facilities.WcfIntegration
Castle.MicroKernel
Castle.Services.Transaction
Castle.Windsor

What I am finding is that Castle.Facilities.WcfIntegration references
a different version of windsor than other parts of the stack.

There now appear to be 3 different versions of Castle.Core.

I am finding it very difficult to keep track of what is getting on.

Horn has been getting some good pull requests from some castle
contributors and I really want to encourage this.

If we can further use horn to help then we should.

Can we do anymore to alleviate what is quickly turning into a maze of
dependencies?

Don't forget, this situation is intensified as other OSS projects use
parts of castle.

I had to pull the plug in updating my stack with Castle, Nhibernate,
boo, MVCContrib and Rhino because I was about to throw my laptop
through the window,

The bits are just not fitting together.

Paul



-- 
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.

Reply via email to