Hi,
We were testing our solution that controls the classic Infragistics ASP.NET Controls with Firefox 10. It seems that they are not compatible with Firefox 10. Are there plans on making them compatible with Firefox 10?
Thanks,
Norman
The classic UltraWebToolbar is having same error as WebCombo (i have version 8.3). My friend tell me : the problem lies in the code developer extract the major and minor version from Page.Request.Browser.version
string version = this.Page.Request.Browser.Version; int num = Convert.ToInt32(version.Substring(0, 1)); int num2 = Convert.ToInt32(version.Substring(2, 1));
So with Firefox 10 with version string like 10.010.0 , version.Substring(2, 1) = '.' will cause the error
[FormatException: Input string was not in a correct format.] :(
we are facing the same problem!
When will there be a hotfix available? This is rather urgent!
Regards
Hi Pro's of Mozilla bugs Fixer's My problem is i cannot open my Web Application in mozilla latest browser 18.0.2 whcih works fine in Mozilla 9.0.1 ... i dont know how to fix ... I tried my max and now i bugged up solving that issue .... please get me out of this big issue...Coming to my issue : I am using Infragistics grid view controls on which page i am getting error's ... i think it might be because of Infragistics Grid views.I am getting an error saying ::::Input string was not in a correct format.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.FormatException: Input string was not in a correct format.Source Error:An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:[FormatException: Input string was not in a correct format.]System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +9591147System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +119System.Convert.ToInt32(String value) +48Infragistics.WebUI.UltraWebListbar.UltraWebListbar.getRenderer() +243Infragistics.WebUI.UltraWebListbar.UltraWebListbar.get_IsAppStyling() +28Infragistics.WebUI.UltraWebListbar.UltraWebListbar.OnPreRender(EventArgs e) +72System.Web.UI.Control.PreRenderRecursiveInternal() +103System.Web.UI.Control.PreRenderRecursiveInternal() +175System.Web.UI.Control.PreRenderRecursiveInternal() +175System.Web.UI.Control.PreRenderRecursiveInternal() +175System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2496Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
Thanks alot :-) You saved my time . Above solution works for me
Thank you so much for your quick response. The way you put it makes total sense to me and helped me just make the decision to plan on moving to 11.1.
Mike
Mike,
Since you may not receive an answer for weeks I thought I would let you know my answer.
I had to upgrade to the latest service release of 11.1 in order to get a fix. It is my understanding that this was the last release to contain the classic controls so I would imagine any future fixes would be applied tot hat build as a service release as well.
I can not believe they are going to stop supporting classic controls and leave people high and dry.
The service release that fixed it for me was. - 11.1.20111.2178
signed,
Fellow developer
Hello-
I see where this fix has been applied into the ASP.Net 11.1 version of controls. Is there any options for dealing with this issue in 10.3? I understand that 11.1 is not going to be supported as of June 2012, so I would like to avoid upgrading to 11.1 just to deal with this issue.
Mike Reynolds