Hi,
we are currently having problems with premature execution of CanExecute (System.Windows.Input.ICommand.CanExecute(object)) on our custom asynchronous ICommand implementation. Unfortunately, we cannot base our asynchronous ICommand on your DelegateCommand (Telerik.Windows.Controls.DelegateCommand). Our research has shown that this problem (and other problems like memory leaks) can be solved by using a WeakEventHandlerManager implementation. Frameworks like Prism are implementing such a WeakEventHandlerManager.
In general, we would like to keep our dependencies in our projects as low as possible, hence avoid referencing Prism or other libraries implementing a WeakEventHandlerManager. We have found in several forum posts (see below), that UI for WPF is implementing the internal static class WeakEventHandlerManager (Telerik.Windows.Controls.WeakEventHandlerManager), but is inaccessible to us due to its protection level.
http://www.telerik.com/forums/custom-appointment-validation#31FR5-6S9UGnhsD0Fcbzyw
http://www.telerik.com/forums/random-com-exception#RAVYUzxVokKq-46Gm1Q9qA
I am asking you to change the visibility of your WeakEventHandlerManager to public, so we can benefit from it without introducing an additional dependency in our projects just for the sake of this one helper class.
Please see the associated Feature Request: https://feedback.telerik.com/Project/143/Feedback/Details/213908-make-weakeventhandlermanager-public
Best Regards
1 Answer, 1 is accepted
Indeed this looks like a valuable improvement for the Telerik WPF suite. I am changing the status of the feedback item to "Approved". You can follow it in order to track which of the future releases will contain the change. I am adding 1000 Telerik points to your account for submitting this feature request.
Regards,
Ivan Ivanov
Telerik by Progress