Allowing properties to represent required dependencies

[cneu...@gmail.com]

Will anyone find it useful if I add a RequiredAttribute the
Castle.Core which
when applied to a property will make it a required dependency. This
reason
I would like this is to reduce the effect of adding a required
dependency to
a base class via the constructor and then having to visit all the
derived classes
constructors as well. This can occur with often with Controllers.

[Hamilton Verissimo]

Will you built this support directly on the MicroKernel?

--
Cheers,
hamilton verissimo
ham...@castlestronghold.com
http://www.castlestronghold.com/

[Craig Neuwirt]

Yes, I plan to do that

[Hamilton Verissimo]

Are you going to change the property-something-contributor to inspect
for the attribute and set the dependency model to Optional=false?

My only concern is that it will be a GetCustomAttribute or IsDefined
call -- which is one of the most lengthy operations -- per public
instance property that will affect everyone. Therefore I'm fine with
the attribute, I'm not fine with this on the MicroKernel.

[Craig Neuwirt]

On 7/12/07, Hamilton Verissimo <ham...@castlestronghold.com> wrote:

Are you going to change the property-something-contributor to inspect
for the attribute and set the dependency model to Optional=false?

 

My only concern is that it will be a GetCustomAttribute or IsDefined
call  -- which is one of the most lengthy operations -- per public
instance property that will affect everyone. Therefore I'm fine with
the attribute, I'm not fine with this on the MicroKernel.

 

Ok, so how about another contributer that will examine the property

dependencies and adjust the Optional flag after reading the attribute.

It will not be a default contributor though

[Hamilton Verissimo]

On 7/12/07, Craig Neuwirt <cneu...@gmail.com> wrote:
> Ok, so how about another contributer that will examine the property
> dependencies and adjust the Optional flag after reading the attribute.
> It will not be a default contributor though

Cool ! :-)