FIX: A System.Xml.Xsl.XsltException exception occurs when you try to perform an XSLT transformation by using an XSLT style sheet that uses the format-number function (832757)
The information in this article applies to:
- Microsoft .NET Framework 1.1
SUMMARYYou create an Extensible Stylesheet Language Transformation (XSLT) style sheet that uses the format-number function. In Microsoft Visual Studio .NET, when you perform an XSLT transformation that uses this style sheet to try to convert positive numbers to strings, a System.Xml.Xsl.XsltException exception occurs. To resolve the problem, download and install a hotfix. To obtain the hotfix, contact Microsoft Product Support Services.
SYMPTOMSYou can create an Extensible Stylesheet Language
Transformation (XSLT) style sheet that uses the format-number function. In
Microsoft Visual Studio .NET, when you try to perform an XSLT transformation by
using this style sheet to convert positive numbers to strings, you receive the
following error message: An unhandled exception
of type 'System.Xml.Xsl.XsltException' occurred in
system.xml.dll If you handle the exception to display the inner
exception and the exception message, you receive the following
output: System.ArgumentException:
NumberGroupSizes Parameter name: Every element in the value array should be
between one and nine, except for the last element, which can be zero. at
System.Globalization.NumberFormatInfo.CheckGroupSize(String propName, Int32[]
groupSize) at System.Xml.Xsl.XsltCompileContext.FormatNumber(Double value,
String formatPattern, String formatName) at
System.Xml.Xsl.FuncFormatNumber.Invoke(XsltContext xsltContext, Object[] args,
XPathNavigator docContext) at
System.Xml.XPath.XsltFunction.InvokeFunction(XPathNavigator qy,
XPathNodeIterator iterator)
Function 'format-number()' has
failed. RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
--------------------------------------------------------------
03-Dec-2003 19:43 1.1.4322.978 1,339,392 System.xml.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.REFERENCES For additional information, click the
following article numbers to view the articles in the Microsoft Knowledge Base:
824684
Description of the standard terminology that is used to describe
Microsoft software updates
307494 How to apply an XSL Transformation to XML for streaming by using Visual C# .NET
For more information, visit the following
Microsoft Developer Network (MSDN) Web sites:
Modification Type: | Major | Last Reviewed: | 4/7/2006 |
---|
Keywords: | kbQFE KBHotfixServer kbBug kbformat kbstyle kbXML kbSample kberrmsg kbcode kbfix KB832757 kbAudDeveloper |
---|
|