Speaking from an entirely different perspective, in applications
there's a logical split between the presentation layer and the
backend. Clearly Core and ActiveRecord are firmly in the backend
space. Excluding Silverlight, the built-in .NET presentation layers
are WinForms, WPF, ASP.NET, and MVC. I don't think people would be
very happy about including references to System.Windows.Forms,
PresentationFramework, or even System.Web.Mvc. ASP.NET support came
along first, but what makes it any different from the other
presentation layers? Clearly Microsoft thinks it's not part of the
core .NET functionality. Though it has a history, it does seem a bit
odd that the Castle framework core should need to be tied to a
particular presentation layer, via non-essential classes.
Patrick Earl
--
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.
