Is ComponentBehavior will be removed forever?

[ktu...@gmail.com]

Hi everyone,

I saw that ComponentBehavior and ComponentBehavior.Castle was removed
from repository, is it still in fixing progress or those libraries
will be removed forever? or am i missing something?

Best Regards
ktutnik

[José F. Romaniello]

Hi Ktutnik and thank you for your interest.

We are droping support for ComponentBehaviors because we feel there are better solutions out there (the old code is in a branch).

It is no longer my recommendtion to use DynamicProxy with the WPF binding infrastructure, because WPF binding use a lot of reflection. There are some workarrounds that Marco Amendola wrote on his blog but i don't like this.

Better tools;

for INotifyPropertyChanged:

   http://code.google.com/p/notifypropertyweaver/

   http://jfromaniello.blogspot.com/2011/01/notifypropertyweaver-new-killer-of.html

for IDataErrorInfo:

  implement on your base view model 

for IEditableObject:

  i wrote an aspect with postsharp, using field interception, in about 20 line of code. However I've never used this interface in real application.

All the afore mentioned tools work for WPF and SL.

About using entities as viewmodels, my general advice is to think twice. But these things are great for viewmodels.

2011/1/15 ktu...@gmail.com <ktu...@gmail.com>

[Ketut Sandiarsa]

Thanks José,

actually i realize that the library was missing after i read your blog (the link that you sent).

too bad, because i think the library was great, regarding Marco's Blog I never used interface for viewmodel because NotifyProperyChangedBehavior never work with interface proxy. but maybe it is a little bit out of nhibernate scope.

anyway, i trust for what you guys done, because you are the man

just keep up the good work :)

Best Regards

ktutnik

[José F. Romaniello]

Thanks Ketut; I strongly believe in this new project NotifyPropertyWeaver, it has many configuration flavors and even work with pre-existing scenarios.

Also can handle readonly properties as:

public string FullName{

  get{ return FirstName + " " + LastName; }

}

It adds a notification for FullNAme in firstname and lastname

And it is static compiled.. .so no proxy, no ioc no nothing...

just new Person and it implements INotifyPropertyChanged in the best way possible.

I've scenarios where i completely forgot about INPC, having logic inside properties set. The weaver can handle that an inject right where it has to be injected.

So I directed all my support for this project (well i fix a minor bug so far :P) and we are working on something bigger with Simon (NotifyPropertyWeaver author).

2011/1/15 Ketut Sandiarsa <ktu...@gmail.com>

[Ketut Sandiarsa]

Thank you,

Sounds great, I will try that library asap.

best regards

ktutnik