.Net Gate

Japaton <a href="http://bit.ly/eRCPKY?jh">buy viagra</a> erin Itantor

People will not have complications with their speeches essay paper writing, because the writing organizations are able to sell research papers of high quality.

Make your life more easy get the credit loans and everything you need.

Thanks Robert for detailed anwesr,All anwesrs are very interesting to me,I agree with most of your points.Regarding DependencyObject   will take into account your warning. Actually I develop few software products, one extends DO, another not. After your comment I consider to remove it as actually it does nothing valuable.What is your view about using Dispatcher in ViewModel?DispatcherTimer?If we are using one of them   can we say we use too much of WPF view layer paradigm in VM?AOP   really interesting pattern, I watched some screen casts some time ago, but I try to avoid  magic  in the code. But if the magic can be supported, I will reconsider this   I just need a time/practice to decide that for me.Another problem I really see   as you mentioned   is supporting thousands lines of boilerplate code. I agree this needs to be solved. I solved it another way. I expose  real  BOs in VM properties. BOs don't raise for me property change notifications but they raise some custom property change events   BOs are CSLA BOs. I wrote a set of controls allowing me to access any property on BO from XAML, some controls are invisible   and just operate with property values and do the work of listening to BO changes, and pushing values to BOs; others are visible like TextField, ComboBoxField, SearchComboField, RepeaterField, CheckBoxField, TemplateField, UniField etc..But I understand that I am lucky that CSLA has custom event notifications.What I still don't like with dynamic approach is.There is no chance of catching the moment when BO changes properties itself. Suppose we change one property on BO, and BO itself will change another property.Now if we define that in VM   that will be failure of VM   this is business logic and it should be places in BO. VM has just to listen to BO state and should not know what BO will change when we set some property to it.So from the above I can conclude: There is no way dynamic properties can solve problem of UI listening to BOs. The only way is BOs actually raising some kind of events   it does not matter   will it be INotifyPropertyChanged or other one. But without that we have to do  hacks  that ruin architecture.And lastly many thanks for pointer to  Layer Supertype  will definitely look into this, sounds very interesting.Thanks for interesting discussion,Kirill

<a href=http://www.cafb29b24.org/docs/buyativan/#56391>ativan anxiety</a> side effects ativan xanax - ativan 2 mg/ml