We've encountered a problem with WARP and WebTab that seems to be what is documented by this post:
http://news.labs.infragistics.com/forums/t/2440.aspx
and a couple more like the post above pertaining to WARP. We think that the async postback functionality of WebTab and WARP make them susceptible to a new error that manifests after installing .NET Framework 2.0 SP1. These errors don't manifest under .NET framework 2.0 without the service pack.
We have a support request in, if we could just get IG to take it seriously. Seems they tested under .NET framework 2.0 without SP1, didn't see the error, and don't think there's a problem. We've followed up with them to let them know about the problem being specific to SP1. Hopefully, we'll see some response soon.
To validate the SP1 issue, we created a test project under VS2005 and VS2008 using CLR 2.0 versions of IG ASP.NET 7.1, then ran it against machines configured with .NET 2.0, and .NET 2.0 SP1. As I mentioned before, the problem manifests under SP1, but not under the non-SP1 2.0 install.
-Jason
Just a followup to this thread for general consumption.
We have now confirmed that WebTab (and WARP?) behave differently under .NET framework 2.0 SP1 than under .NET framework 2.0 RTM (without SP1).
If you have installed VS2008, you may find that your .NET framework 2.0 HAS been updated to the SP1 release, and you may not realize that this has been done. According to Microsoft, .NET framwork 2.0 SP1 is regarded as a prerequisite for .NET framework 3.5 on the same machine.
If you want to ROLL BACK to .NET framework 2.0 RTM (non SP1) you must UNINSTALL .net framework 3.5, and then uninstall .NET framework 2.0 SP1 before you will be able to re-install .NET framework 2.0 RTM (non SP1).
For more information on this, please see the following thread on Microsoft's support forums:
http://forums.microsoft.com/forums/ShowPost.aspx?PostID=2958260&SiteID=1
Jumping in here...
I have been trying to get resolution on a number of similar problems. I place a variety of Netvantage controls inside the ASP.net FormView control to handle drop down lists, editting controls, webgrids, and A nifty Tool bar to do all the FormView actions, etc, all inside an AJAX update panel.
This worked fine until the .net 2.0 sp1 update installed back in late January. Since then, none of my forms are working that have an AJAX update panel with any Netvantage control in it.
In addition, AJAX controls from Netvantage (WARP panel and Async features of WebTab) are all giving similar errors.
After several goes with Support trying to convince them this was not just a fluke, they finally initialized an investigation with the engineers. That was back on Feb 12,2008. Nothing since then.
I hope they are indeed working on this problem.
I had to strip all the AJAX capabilities out of my project and modify code where required to make the pages work again. This has been a very frustrating time for me, and my customers are losing confidence in my product.