Well, Oliver, that's why I'm posting here. I'm trying to see how it could
be done to eliminate those lines of code inside the method.
As for practicality, the example given could be used to attach the attribute
to any number of methods that each update a part of an employee's profile.
The attribute could describe the method of notification that needs to be
sent out, the urgency, the format... any number of things (the example I
posted only uses one property for the attribute). The attribute itself has
nothing to do with the main intent of the method, to do the update to the
record, it only "attaches" some other behavior to the method.
I'm looking at doing maybe declarative event handling on a base class,
seeing if that will work.
"Oliver Sturm" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello Random,
>
> I'm sorry - I may be dense, but I really can't imagine what this would be
> good for. Can you describe a practical example of how this is going to be
> used once it's finished?
>
> Plus, you don't answer part one of my previous question - what do you want
> to "automate"? As I said, if you're going to handle the value from the
> attribute inside the method, you'll need to have at least that one line
> that pulls that value into a local variable. What do you imagine how you
> could get rid of that single line?
>
>
> Oliver Sturm
> --
> http://www.sturmnet.org/blog