There is a blog post by Rocky here talking about IdentityConverter and WPF:
The Csla.Wpf namespace in CSLA 3.8 contains the IdentityConverter class.
In CSLA 4.1, the Csla.Xaml namespace for Silverlight does not appear to contain the IdentityConverter class and this is the only forum post I can find mentioning IdentityConverter and Silverlight, but the issue appears to remain unsolved:
I'm porting a WPF CSLA 3.8 project to Silverlight CSLA 4.1 and I'm having issues with databinding and I'm not sure if the lack of IdentityConverter could be causing the issue. Thoughts?
WPF 3.5 introduced a binding option that solves this problem, so I removed IdentityConverter from CSLA at that point. I don't recall the specific binding option off the top of my head, but there's a way to tell the binding to always refresh.
To my knowledge, Silverlight never had this same issue, I think it was only a WPF binding problem.
IdentityConverter still exists in CSLA 4.1 in the Csla.Xaml component for WPF.
I have now confirmed that the problems I was having were not related to IdentityConverter, so my problem is solved although I'm still interested to learn the specific binding option introduced in place of the need for IdentityConverter.
Copyright (c) Marimer LLC