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
The version utility does not offer the option to upgrade to 11.1, it only offers 11.2.
Anyone have any ideas on how to go from 10.3 to 11.1?
Hello elPlato79,
That is because you have probably downloaded Version Utility for 11.2. In order to use Version Utility for 11.1 you should install 11.1 product first.
You can also upgrade your project manually by replacing the 10.3 assemblies and references with 11.1 ones.
Right now there are plans for creation of Untested Build addressing this issue for version 10.3 also, that is why you can wait for this build too.
Hello All,
The reported issue was researched and addressed from our R&D team and it is resolved in our latest service release for ASP.NET.
You can see our latest service releases in our web site - “Support > Service Releases” and download them from “My IG > My Keys and Downloads” page.
If you cannot see/download our latest service release you may need to register your product key first. You can register your product key in “Support > Register Your Product” page.
Thank you for your patience.
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
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
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