I think the Fluent API could indeed do with some rationalization.
One of them being getting rid of as many strings as possible, such as
replacing :
.StartUsingMethod("Start").StopUsingMethod("Stop");
to
.StartUsingMethod(x => x.Start()).StopUsingMethod(x => x.Stop());
Another thing (ps: I'm no advanced Castle user), I mentioned to
@kkozmic over twitter about the ability to create concrete
implementations out of only interfaces.
So for instance with interface IMyAppSettings {public int TimeOut
{get;}}, one could declare either at Method (or Type) level attributes
that will tell Castle how to create a proxy inheriting IMyAppSettings.
For instance, IMyAppSetting.TimeOut might be coming from an
AppSettings value, you'd have an attribute that would tell Castle how
the getter will be actually implemented, using convention or not.
Daniel
--
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.
