On Sept 14 I applied the latest service pack for NetAdvantage 2011.1. Afterward the WebDataMenu, WebExplorerBar and WebDataTree controls will not render.
All the other controls appear to work.
I attached a screenshot of Visual Studio (2010) showing the ill-rendered controls in the designer; the source (showing the correct version of the controls in the Register Assembly); and the references (right side of screen) with the version number that matches the register assembly in the source).
There is a tooltip when I hover over the <ig:WebDataTree... control that states the following:The base class includes the field "WebdataTree1", but its type (Infragistics.Web.UI.NavicationControls.WebDataTree) is not compatible with the type of control (Infragistics.Web.UI.NavigationControls.WebDataTree).
Some assistance with this would be very much appreciated!
Incidentally I originally had this problem on a project that I had upgraded from Infragistics 2007. I just tried adding those controls into a new web project and the same error occurred, so I can't pin it on the old project not being upgraded properly.Could it be a problem with the service release?
Hello,
I have investigated your issue and, I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID’s of 88667,88668 and 88669. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
I will leave this case open and update you with any new information after the review. You can also continue to send updates to this case at any time.
You can view the status of the development issue connected to this case by going to the “My IG” tab on our website, hovering to the "My Support Activity" dropdown and selecting the "Development Issues" tab.
Please let me know if you need more information.
It has been nearly a month, is there an update on this?
I'm still getting it
Hello All,
This issue has been resolved in the latest service release of 11.1.
Please let me know if you have any further questions regarding this matter.
Hello Rickycl,
This issue has been addressed and fix will be in next service release which is projected to be released in the mid to end of November. Please note that this may be delayed due to some unforeseen issues.
I have opened a support request (CAS-76526-2XW3JT) for this forum post to provide you an untested build. Please use the following link to log onto your account at Infragistics.Com:
<https://ko.infragistics.com/Membership/MySupport.aspx>
Once you are logged onto your account, go to My Support Activity to view the progress of this support request. An update will be sent to you in the support request with any new information we find.
Please let me know if you have any questions.
Hi,
We are having the exact same problem, how could we get the update to the service?
Thanks in advance.
Yes, it turned out to be a problem with the service release. Infragistics was able to re-create the problem in their labs, after spending an hour with me in a remote session.
Two weeks ago Infragistics issued me an update to the service release that addressed the problem, and mentioned they would be incorporating the fix in their next service release.