Click here to Skip to main content
13,141,429 members (23,912 online)

Comments by Siavash Mortazavi (Top 6 by date)

Siavash Mortazavi 6-Dec-11 3:38am View
Thank you for your solution and sorry for the late reply ;)
Surely your solution works great, but the reflection technique is much slower. I think if the performance is not an issue in your project, your solution is more managable than mine ;)
Siavash Mortazavi 22-Jul-11 23:26pm View
About "it doesn't really remove maintenance concerns", you're completely right Daniel ;)
It's not an ultimate solution, but maybe better than nothing :)
Thanks for posting linq expression tip.
Siavash Mortazavi 21-Jul-11 9:04am View
You're right Doc ;)
Thanks for your tip :)
Siavash Mortazavi 21-Jul-11 9:03am View
You're right Doc ;)
Thanks for your tip :)
Siavash Mortazavi 21-Jul-11 0:08am View
As you said, yourself, Reflection in to slow; maybe it's not a wise idea to use it in big projects.
And there is another problem with this method: in your method we can't refactor the process of raising the event in a separate method (e.g. RaisePropertyChanged), because if so, the reflection will return the name of the method, itself.

I haven't ever taught of using reflection this way, thanks a lot for sharing your knowledge ;)
Siavash Mortazavi 28-Jan-11 9:42am View
Reason for my vote of 5
It seems it's one of the best approaches to load dynamic data into wp7 apps. tnx;)

Advertise | Privacy |
Web01 | 2.8.170915.1 | Last Updated 1 Jan 1900
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid