Mostly it would require:
- Ensuring all tests run under Mono
- Add Mono build to CI server
- Provide Mono Binaries (?)

...anything else?

All the current documentation in the website refers to previous versions. In some pages it says that the lastest version in version 1 RC 2.

when I have
public class Foo:IFoo{}
public class Bar:IBar{}

both of which are service contract implementations I want to be able to host them both in a single service host with two endpoints exposed : IFoo & IBar forwarding calls to appropriate implementation.

Release an official version even it is necessary to document the known problems or limitations. Uptake and feedback should increase if more people are using it. Many places unable to get buy in from management if they have to get it from the trunk.

Those of us who use MonoRail and ActiveRecord are still committed to using trunk. However, those of us who don't don't really need that much that's trunk-only these days, except for NHibernate and Logging.

A version for the client side for the WcfFacility that supports Silverlight

("We" in this case meaning "various members of the Castle Community" not necessarily involving me). I see it as one of those Wrox-multi-author-picture on the cover book, with maybe 5 major divisions (Windsor/Monorail/ActiveRecord/DynamicProxy/et al), with each of those having 5-10 chapters. (I'm sure Krzysztof can edit his blog series on DP into 5 chapters in about 2 hours) It will be a great "marketing" tool for the Castle stack, and focus us on bring all our far-flung documention into one place.

The Castle Generator seems powerful yet very undocumented

Please include in each project's release its sample application from /trunk/Samples (new samples are also welcome).
This will help the new users to start using the projects.

For performance reasons it would be good to support indexes on foreign keys (BelongsTo) in ActiveRecord. NHibernate already supports this so it should not be difficult.

Add validator that would check if property/field of enum type is one of defined values

So I can port #moq too :)

I'm talking about DynamicProxy here, but it's probably similar in other projects.
Using debugger with DP is not as neat as it could be. Certain types should have DebuggerDisplayAttribute or debugger proxies... Do you think that's useful? Is there anything else you'd wanna see, or any particular types that need this?

allowing intellisense for creating the configuration files.

The perception is that many other containers are "lightweight"...I believe this perception has more to due with the number of assemblies (portability) than the lines of code or architecture.

Given the very common usage of Caslte + Windsor, I'd like to see a merged version so that Windsor usage would require just a single assembly.

In the case where a project isn't using Windsor the code would simply go unused much like the majority of the BCL that we don't use everyday but still travels in the assemblies.

Hi,
Have you got any plan for porting Dynamic Proxy to Silverlight ?

Type Wrapping would allow to wrap a type with another type (without inheriting from it) and mimic it's public interface (without overriding it) to add dynamic proxy capabilities to sealed methods/classes. This would work with scenarios that don't rely on the actual type, like WPF data binding or C# 4.0 dynamic.

More on it here: http://using.castleproject.org/display/CASTLE/Dynamic+Proxy+3+design+meeting

Suggesting www.shadows.com for one of your demos is not good. I happened to be fortunate enough to check that one out while at work and was presented with a neat trap.

See http://www.castleproject.org/castle/whoisusing.html and click the link for the shadows showcase.