> when do we start building for .net 4.0?
>
> there are some things there I would like to start taking advantage of (for
> example optional arguments would impact Windsor's constructor matching)
> it could also be used for service overrides, like below, although this is
> probably not the best idea.
> [DefaultValue("someFooKey")]
> public IFoo OptionalFoo { get; set; }I think the new expression trees (<http://www.re-motion.org/blogs/mix/archive/2010/02/18/.net-4.0-expression-trees-code-gen-blocks-and-visitors.aspx>) would be quite suitable to replace DynamicProxy's AST. (They are much more complete and more robust than DP's own.) Using them would only be an option once we stopped supporting .NET 3.5, however - and that's likely to take a while :) Fabian -- 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.
