VS2008, IG controls 7.1, .NET 2.
I have an UltraWebToolbar control on the form with 4 buttons (the control is inside a WARP) -
<igtbar:UltraWebToolbar ID="tbAdv" Width="200" runat="server" OnButtonClicked="tbAdv_ButtonClicked"> <Items> <igtbar:TBarButton Image="opendir.gif" Text="Open" Key="open"> <Images> <DefaultImage Url="opendir.gif" /> </Images> <DefaultStyle CssClass="tb_d" Width="56px"> </DefaultStyle> </igtbar:TBarButton> <igtbar:TBarButton Image="save.gif" Text="Save" Key="save"> <Images> <DefaultImage Url="save.gif" /> </Images> <DefaultStyle CssClass="tb_d" Width="56px"> </DefaultStyle> </igtbar:TBarButton> <igtbar:TBarButton Image="Save.gif" Text="Save as..." Key="saveas"> <Images> <DefaultImage Url="Save.gif" /> </Images> <DefaultStyle CssClass="tb_d" Width="80px"> </DefaultStyle> </igtbar:TBarButton> <igtbar:TBarButton Image="find.gif" Text="New" Key="new"> <Images> <DefaultImage Url="find.gif" /> </Images> <DefaultStyle CssClass="tb_d" Width="56px"> </DefaultStyle> </igtbar:TBarButton> </Items> </igtbar:UltraWebToolbar>
Clicking on any of the buttons gives a javascript error like the following -
Line: 69692273Error: Syntax error
The line number is random but is usually in the millions! Clicking 'Yes' to debug just clears the error (it won't debug). The button click does post back and the error appears after it has.
EDIT: Adding <xhtmlConformance mode="Legacy"> to the web.config seems to fix it, but this isn't ideal...
Just an fyi -- removing the .Net Framework 2.0 SP1 and replacing with just the .Net Framework 2.0 cleared up the problem when using my PC as a localhost for our web site.
Hi,
I tested those codes inside of WARP (empty implementation of tbAdv_ButtonClicked). I did not get any errors. Though, I tested current/latest version of controls.
If page contains MS validators, then under SP1 or VisualStudio2008 the older version of Shared.dll would produce similar error. That happened because dot-net changed logic to render javascript of its validators. That problem in Shared.dll was fixed few months ago. I guess it should be already in hot fixes.
That rings a bell... I have .NET 2 SP1 and I think it started happening then...
Maybe something to do with this?
http://support.microsoft.com/kb/931795/
can you tell me what is the .NET framework installed on your machine ?
We also had similar kind of problem, but at that time we have .NET framework 2.0 service pack1 installed on our machine. so when we uninstalled Servicepack1 and installed just the .NET framework 2.0 .It worked for us..