Basic Search  Advanced Search   
Topics Resources Free Library Software XML News About Us
home » info bank » .NET XML KB Articles » BUG Fri, Jul 13, 2007
.NET XML KB Articles


Page: 1  2  3  

Data Loss When You Recursively Navigate an XmlDataDocument
KB: 325690
When you try to recursively navigate an XmlDataDocument that has been synchronized with a filled ADO.NET DataSet, all of the data is not returned.

A problem exists in the XmlDataDocument implementation of the RTM release of the Microsoft .NET Framework.

To work around this problem, access the InnerText property of the XmlDataDocument object before you recursively navigate it. You can also use the GetXml method of the DataSet object to load the XML representation of the DataSet data in an XmlDocument object and navigate it recursively.
View this KB Article...

XmlNamespaceManager Does Not Correctly Atomize Strings During Namespace Lookups
KB: 324996
The LookupNamespace and LookupPrefix methods of the XmlNamespaceManager class may return a null value even when a matching namespace definition has been added to the XmlNamespaceManager object. This problem is only noticed when you use the NameTable of an XmlDocument to construct the XmlNamespaceManager object instance.
View this KB Article...

Position() and Last() XPath Functions Are Ignored When You Use Them as XSLT Function Arguments
KB: 324033
The position() and last() XPath functions are ignored when you use them directly as XSLT function (standard, script, and extension function) arguments in XPath query expressions that are used in XSLT style sheets.

The XPath processor executes the XSLT functions before it sets the context of the position() and last() XPath functions.

Use XSLT variables to store the values that these functions return. You can then use the XSLT variables as the XSLT function arguments in XPath query expressions that are used in the style sheet.
View this KB Article...

No Error Message About Duplicate SOAPAction Values Until First Invocation of Service
KB: 323575
When the RoutingStyle property of an XML Web service is SOAPAction, the SOAPAction values must be unique across the methods on the XML Web service. However, you do not receive an error message about duplicate SOAPAction values until the first invocation of the Web service, although you should have received the error message at Web Services Description Language (WSDL) generation time.
View this KB Article...

Error When You Invoke Methods on a Web Service by Using ASP
KB: 322886
When you invoke methods on a Web service, you may receive the following error message:
System.InvalidOperationException: Unable to generate a temporary class
(result=1). error CS2001: Source file 'C:\WINNT\TEMP\gggcyckb.0.cs' could not 
be found error CS2008: No inputs specified at 
System.Xml.Serialization.Compiler.Compile() at 
System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings) at 
System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings) at 
System.Web.Services.Protocols.SoapClientType..ctor(Type type) at 
System.Web.Services.Protocols.SoapHttpClientProtocol..ctor() at 
SDAccounts.swd_dotnetdev.Organizations..ctor() at 
SDAccounts.Contacts.GetContactInfo(Object Status, Object& ErrorString)

ASP.NET Web Services sometimes use the system Temp folder when they process WebMethods. If the thread that is processing the request uses an Identity that does not have read/write access to that folder, you receive the error message.
View this KB Article...

XML Serialization Incorrectly Processes MaxOccurs="0"
KB: 319922
You can use the XML Schema Definition Tool (Xsd.exe) to generate the common language runtime classes from an XML schema. When you do so, elements that have the maxOccurs attribute with a value of "0" is supposed to be ignored. However, they may be included in the classes that are generated. When you generate the corresponding DataSet classes, the element is generated as a column.

The DataSet.ReadXmlSchema method also incorrectly interprets the XML schema when the schema contains elements that have maxOccurs="0". This means that the DataSet.ReadXmlSchema method does not ignore those elements.

If an element has maxOccurs="0", the correct interpretation from a relational view is "this column does not exist". But the element is not ignored and included in the runtime class that is generated or the DataSet class.
View this KB Article...

Web Method Parameters Are Mismatched if You Pass a Null Parameter When You Call a Web Service
KB: 318037
ASP.NET XML Web services allow you to control the formatting and call style of methods in a Web service. You can control this behavior by using attributes applied to the Web methods in the Web service. However, values that are incorrectly matched with the parameters in the Web service may be passed to the Web service by a .NET client. For example, the Web service may serialize the second parameter passed by the client into the first parameter of the Web service.
View this KB Article...

Compile Error Message When You Add a Web Reference to a Managed Extensions for C++ Application
KB: 317807
When you add a Web reference to a .NET Web service (.asmx file) in a Managed Extensions for C++ application, you may receive a compile-time error message similar to the following:

Creating web service proxy file...
Error: Cannot find definition for http://test:test. Service Description with namespace http://test is missing.
Parameter name: name
If you would like more help, please type "wsdl /?".
error CS2001: Source file 'Server.cs' could not be found
fatal error CS2008: No inputs specified
The system cannot find the file specified.

You do not experience this behavior when you add the Web reference in a Visual C# .NET application or in a Visual Basic .NET application.
View this KB Article...

XmlSchema Rearranges the Positions of Annotation and Include Elements
KB: 317707
XmlSchema rearranges the positions of xs:annotation and xs:include schema elements when those elements are intermingled in an XML schema so that all of the xs:include elements are brought to the beginning.
View this KB Article...

Type '###' Is Not Declared in Reference to Local Type of an Included XSD Schema File
KB: 317611
The current implementation of XSD schema-validation support in the .NET framework does not convert the targetNamespace of the local referencing type of an included XSD (it does not support the "chameleon" include). The following error message is returned:

"Type 'testType' is not declared." in c.xsd
View this KB Article...

XmlTextReader Decodes URLs Before Downloading Resources Resulting in Unpredictable Behavior
KB: 317610
When you use the XmlTextReader object to download resource files, the reader decodes the URL for the resources. If the URL contains any special characters (for example, ampersands or percent signs), this may result in unpredictable behavior.
View this KB Article...

A Typed DataSet That Imports a Secondary Schema Cannot be Used As a Method Parameter or As a Return Type with ASP.NET Web Services
KB: 317340
You cannot create a Web service proxy when the Typed DataSet that imports a secondary schema is used as a parameter or as a return type from the WebMethod. If you try to do this, the following symptoms may occur:
  • When you generate the Web service proxy class by using the Web Services Description Language (WSDL) tool, WSDL.exe fails. You receive the following warning message and error message:
    Warning: Schema could not be validated. Class generation may fail or may produce incorrect results.
    Error generating DataSet for schema 'SchemaNamespace'.
    where 'SchemaNamespace' is the namespace of the schema.
  • The Visual Studio .NET Web References wizard does not produce a Web service proxy for your Web service. No errors are reported. However, you find that the References.cs file or the References.vb file (that contains the proxy definition) do not exist. Also, the client application cannot declare instances of the Web service proxy.
When you create the Web service proxy that uses Typed DataSet, the Typed DataSet does not correctly import secondary schemas. Instead of using the expected secondary schema, the returned schema imports a schema with an arbitrary name such as _app1.xsd. Because of an incorrect secondary schema name, the tools such as WSDL.exe or Microsoft Visual Studio .NET cannot correctly create a proxy for the Web service. Also, the returned XML cannot be serialized back to a corresponding Typed DataSet instance. If you try to do this, the result is an XmlSchemaException.
View this KB Article...

targetNamespace of DataSet Instances Is Hard-Coded in Windows Form Constructor
KB: 316839
When you generate a DataSet object from an XSD schema file and then add the DataSet to a Windows Form, the targetNamespace property of the schema file on which the DataSet is based is hard-coded in the "InitComponent" section of the Form. For example, in Visual C# .NET, you can see the following within the private void InitializeComponent() call:
this.dataset11.DataSetName = "Dataset1";
this.dataset11.Locale = new System.Globalization.CultureInfo("en-US");
     //namespace is hard-coded
this.dataset11.Namespace = ""; 
If the targetNamespace in the DataSet schema is changed for any reason, a few scenarios may stop working; for example, writing the DataSet out to an XML file, reading it back in, and persisting the DataSet with the correct namespace.
View this KB Article...

Data Not Sorted When You Use Namespace Prefix in String Passed to XPathExpression.AddSort
KB: 316656
When you use a string to specify the sort key expression parameter in a call to the AddSort method of the System.Xml.XPath.XPathExpression object, the XML data is not sorted. This problem is only noticed when the specified sort key expression contains XML element and attribute names that are prefixed with namespaces. When a string is used to specify the sort key expression, the namespace prefixes are not correctly resolved. This behavior is noticed even when the System.Xml.XPath.XPathExpression object is associated with a System.Xml.XmlNamespaceManager object to which the namespace prefix definitions have been added.
View this KB Article...

"ExternalException: Cannot Execute a Program" Error Message When You Call WebServices from .aspx Page
KB: 315904
If you use Simple Object Access Protocol (SOAP) to call the WebServices method from an .aspx page, the .aspx page may fail when you run the Microsoft Internet Information Services (IIS) Lockdown tool. In addition, you may receive the following error message:

[ExternalException (0x5): Cannot execute a program. The command being executed was "d:\winnt\\framework\v1.0.3408\csc.exe" /noconfig @"D:\WINNT\TEMP\eyrpuhyg.cmdline".] This problem only affects Web applications or Web services that are clients of a Web service and that impersonate the Anonymous user account.

The IIS Lockdown tool denies execution access for the IUSR_COMPUTERNAME and the IWAM_COMPUTERNAME accounts to every executable file (*.exe) in the Windows directory (%windir%). This includes framework tools such as the Csc.exe file, which the XmlSerializer class uses. When a Web application or a Web service impersonates IUSR_COMPUTERNAME or IWAM_COMPUTERNAME, the Web application or the Web service cannot use XmlSerializer to serialize objects into Extensible Markup Language (XML) documents.

NOTE: This problem does not affect the server side of a Web service because XmlSerializer is generated and compiled outside of the impersonation.
View this KB Article...

Page: 1  2  3  

  Contact Us | E-mail Us | Site Guide | About PerfectXML | Advertise ©2004 All rights reserved. | Privacy