>>Well, that seems to do the job.
>
>FWIW, I think your orignal manual setting are the best in this scenario. More straight forward (though you should be calling a SetMyProps() method and do all the settings there) and performs well.
>
>If you've got a thousand or so properties making manual stuff impractical, I'd use AMemebers() to generate the code at design time and plug that in.

Well, during these days, that object is constantly under evolution. So, new properties are being added. So, I need a method which is generic. By that, I won't have to adjust it at each occasion.