I have just spent a significant amount of time debugging
PropertyChanged events that weren't being triggered and was happy to
find this post which describes my problem exactly. The workaround of
not lazy-loading objects is not an option for us so we're stuck with
not having the ability to properly use INotifyPropertyChanged in our
code. The solution of having an interceptor is beyond what we trust
ourselves to do in NHibernate. Has anyone attempted this?
On Sep 25, 10:37 am, "Ayende Rahien" <[EMAIL PROTECTED]> wrote:
> Yes, your solution would be the probably best solution for that.
>
> On Thu, Sep 25, 2008 at 4:43 PM, Artur Dorochowicz <
>
> [EMAIL PROTECTED]> wrote:
>
> > Now that you've described it, it makes perfect sense. Thanks Ayende.
>
> > I use Paulo's solution now, so that it is no issue for me anymore,
> > but, just out of curiosity, are there any possible solutions for this?
>
> > One (cumbersome) that I can see is to use some kind of interceptor as
> > you do in your article, in the model make SendPropertyChanged
> > protected virtual and intercept calls to it. The interceptor, instead
> > of calling the original SendPropertyChanged, would raise the
> > PropertyChanged event but with sender being the proxy object.
> > Could that work?
> > I don't know neither reflection nor castle proxy stuff well enough to
> > go and try to do it myself.
>
> > On 25 Wrz, 11:04, "Ayende Rahien" <[EMAIL PROTECTED]> wrote:
> > > I can most certainly see this being registered on the actual class:
>
> > > + Method {Void OnPropertyChanged(System.Object,
> > > System.ComponentModel.PropertyChangedEventArgs)}
> > > System.Reflection.MethodInfo {System.Reflection.RuntimeMethodInfo}
> > > + Target {System.ComponentModel.PropertyChangedEventManager}
> > > object {System.ComponentModel.PropertyChangedEventManager}
>
> > > And the invocation list contains both of them.
>
> > > The problem, however, is that the sender object that it sends is
> > different
> > > than the proxy.
> > > WPF thinks that it is the proxy that it is handling, while the real
> > object
> > > behind the scene is raising the event, WPF catch that, but has nothing
> > that
> > > match this (because the proxy and the real object are different
> > instances).
>
> > > This is a leaking this issue, I am afraid.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---
