When being targeted by globalInvoke and globalUpdate calls, IAjaxControl instances that use a custom CallbackStrategy (other than the default ControlCallbackStrategy) aren't being loaded correctly.


When ControlCallbackStrategy.LoadGlobalControl creates an instance of the global control (specified by the "controlType" argument set on the client-side), it doesn't check for whether or not the global control implements IAjaxControl. As such, the method currently doesn't call the "LoadControl" method of the global control's CallbackStrategy so any special loading logic for that IAjaxControl will not be performed.


peanutbutterlou wrote Jul 8, 2010 at 12:33 AM

A fix for this will be included in the v1.0.2.0 release of the framework.

wrote Feb 13, 2013 at 2:48 AM