Dec 01, 2014, 9:43 PM
[CLOSED] DirectMethods and error with dynamic controls
Ever since upgrading from Ext.NET 2.2 to 2.5, we have been seeing errors like
An error has occurred because a control with id 'ctl00$c$ctl71' could not be located or a different control is assigned to the same ID after postback. If the ID is not assigned, explicitly set the ID property of controls that raise postback events to avoid this error.
This wasn't an issue before and I can understand where it is coming from. We often create dynamic controls only on initial page load because our pages do not need to do a normal postback. We only use DirectMethods or DirectEvents. Is there a way to tell app not to validate against dynamic controls? I do not need their post data to persist during DirectMethods / DirectEvents.
Note we turn off viewstate on all our pages.
An error has occurred because a control with id 'ctl00$c$ctl71' could not be located or a different control is assigned to the same ID after postback. If the ID is not assigned, explicitly set the ID property of controls that raise postback events to avoid this error.
This wasn't an issue before and I can understand where it is coming from. We often create dynamic controls only on initial page load because our pages do not need to do a normal postback. We only use DirectMethods or DirectEvents. Is there a way to tell app not to validate against dynamic controls? I do not need their post data to persist during DirectMethods / DirectEvents.
Note we turn off viewstate on all our pages.
Last edited by Daniil; Dec 11, 2014 at 7:41 AM.
Reason: [CLOSED]