I recently wrote an enhancement to an that included creating a new user control. I initially added all of the new features in a new web application, before integrating it into the existing application. The new user control within this new application worked great and had a couple of WebDropDowns and WebDatePickers.
As soon as I moved the new code from the project into my existing application, however, it stopped working. Everything worked as expected except for the infragistics controls. They (the WebDropDown & WebDatePicker) would not persist their values, nor would they fire any (server-side) events. I eventually resorted to using the non-Ajax version of the controls (the WebCombo & WebDateChooser). The non-ajax controls worked great....they persisted their values and event-firing worked just as expected.
My resolution was to use the non-Ajax controls, however, I would like to know if anyone else has experienced this problem or knows how to resolve it. The code was exactly the same in both projects and the only difference was that the existing application was a website while the project one was a web application. I was using version 9.2.20092.2025 and had the same problem with .2183.
Hello sliefdg,
I think I may had a case previously where when disabling view state on the WebDropDown will not allow the events to fire so you can set the EnableViewState property to true.
Let me know if this works for you. Thank you.
However, I do thank you for your reply.
Thanks for the update.
You can attach a sample or the aspx markup to the thread on the project not working and I run the application on my machine for verifying the behavior. This will help for troubleshooting.
Let me know if you have any questions with this matter. Thank you.
Thanks for responding to this. I dont think you will have any problem getting this snippet to work. It is the ascx markup for a user control. It works with or without 'enableviewstate' in the project application and does not work with or without 'enableviewstate' in the other application (website). And as soon as I switched to the non-ajax infragistics controls (same version), it began working fine.
<%
%>
<
>
="container">
="100%">
="true">
="separator">
="Claymation">
">
="2005">
="2006">
="2007">
="2008">
="2009">
="2010">
="2011">
="btnUpdate_Click">
="server">
</
This is just a follow up on the thread on whether the same behavior occurs in NetAdvantage 2010 Vol 3. I would like to run a sample for demonstrating events not firing. Which event in particular for the WebDropDown or WebDatePicker is not firing?
I'm having the same problem with 10.3. Was this issue resolved?
I have also the same problem with Infragistics4.Web.v11.1, Version=11.1.20111.1006.
I'm trying to migrate the controls from old ones (WebDateChooser, etc) to the new ones in order to upgrade to version v11.2.This is a showstopper, and we might move to other controls if we don't solve this problem.
With WebDatePicker with OnValueChanged event subscribed, I can see the postback and sending the correct fields:__EVENTTARGET=_ctl0_DialogPlaceHolder_ContactPropertiesCtrl_PersonalGeneralPanel_templateItem_BirthDateChooser
__EVENTARGUMENT=ValueChanged
_ctl0_DialogPlaceHolder_ContactPropertiesCtrl_PersonalGeneralPanel_templateItem_BirthDateChooser_clientState=|0|012011-11-15-0-0-0-0||But debugging the request, the WebDatePicker.Value is null, and the ValueChanged isn't triggered...
Finally, after much frustration, I manage to implement a workaround for this problem.
It appears that WebDatePicker doesn't propagate correctly the value and doesn't trigger the event when the postback is made with a UltraWebToolbar or even a LinkButton.
My solution was to substitute the UltraWebToolbar with a HTML <button> with runat=server.
After this change , the WebDatePicker.Value is correct and the ValueChanged is triggered.