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


Page: 1  2  3  

New Interop DLL Is Not Put in the Correct Location for the Project When a COM Component Is Added
KB: 820126
You can create a .NET Web service by using Visual C++ .NET. The Web service uses the COM component to perform any complex logic. However, when you try to access the Web service method that uses the Component Object Model (COM) component, you may receive the following error message exception in the browser:

System.IO.FileNotFoundException: File or assembly name , or one of its dependencies, was not found.
View this KB Article...

"System.Runtime.Serialization.SerializationException" Exception If You Declare a Static Local Variable in a Method of a Visual Basic .NET Class and Try to Serialize the Object of the Class Using BinaryFormatter or SoapFormatter
KB: 818412
Microsoft Visual Basic .NET allows you to declare static local variables inside a method of class. However, if you declare a static local variable in a method of the Visual Basic .NET class, and then you try to serialize the object of the class by using BinaryFormatter or SoapFormatter, you receive the following exception during run time:

An unhandled exception of type 'System.Runtime.Serialization.SerializationException' occurred in mscorlib.dll Additional information: The type Microsoft.VisualBasic.CompilerServices.StaticLocalInitFlag in Assembly Microsoft.VisualBasic, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a is not marked as serialized.
View this KB Article...

Incorrect Proxy Is Generated When WSDL File Contains Multiple Bindings
KB: 816636
You can generate a proxy class for your Web Service Description Language (WSDL) file that has multiple bindings. All the bindings use SOAP headers. In the SoapHeaderAttribute of the generated proxy class, you may find that only the first binding class has all the required parameters. The remaining classes may not have all the expected parameters in the SoapHeaderAttribute.
View this KB Article...

XSD.exe Generates Classes that Allow Multiple Entries for all Members of Choice Although Only One Member is Unbounded
KB: 816226
In an XML Schema project, the XSD tool incorrectly interprets the maxOccurs attribute for all members of the choice element as unbounded if one of the following criteria is true:
  • If the maxOccurs attribute is set to a value that is greater than 1.
  • If the maxOccurs attribute is unbounded for at least one member of the choice element.
With the managed class that is generated by the XSD tool, multiple unbounded entries can be added for all the members of the choice element in the XML document.

There is no direct workaround for this problem. However, in some cases you can work around this problem by using two choice elements. The first choice element has members with the maxOccur attribute set to one, and the second choice element has members with a maxOccur attribute that is set to greater than one.
View this KB Article...

"InvalidOperationException" Error Message Occurs When You Consume a Web Service with an Out Parameter
KB: 815211
You can use Visual C# .NET to create a Web Service that has a Web Service method with an Out parameter. The Out parameter may appear before the In parameter or the Ref parameter. You must specify the SoapRpcMethodAttribute to the Web Service method to preserve the order of the parameters. The problem occurs when you subsequently use this Web service that you created in Visual C# .NET in a Visual Basic .NET application. You may receive the following error message when you call the Web Service method.
An unhandled exception of type 'System.InvalidOperationException' occurred in system.xml.dll
Additional information: There was an error generating the XML document.
View this KB Article...

"The Operation Has Timed-Out." Error Message May Occur When You Add a Web Service Reference
KB: 815209
When you try to add a Web reference to a Microsoft ASP.NET Web service in Microsoft Visual Studio .NET 2003, you may receive the following error message:

There was an error downloading 'http://<WebServerName>/<%WebServicePath%>/<WebServiceName>'. The operation has timed-out. When you try to create a Web Service Proxy file for the Web service by using the Web Service Description Language tool (Wsdl.exe), you may receive the following error message:

Unhandled Exception: System.TypeInitializationException: The type initializer for "System.Net.Sockets.Socket" threw an exception. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full at System.Net.Sockets.Socket.InitializeSockets() at System.Net.Sockets.Socket..cctor()

Note You do not receive this error message when you run Wsdl.exe that is included with the Microsoft .NET Framework SDK v1.0.
View this KB Article...

Xsd Tool Generates Incorrect Class When XML Schema Has a Group Element in a Choice Element
KB: 815106
You use a group element in a choice element in an XML Schema, and then use the XML Schema Definition Tool (Xsd.exe), to generate a Visual C# .NET class or a Visual Basic .NET class. When you generate the class, the code for the group and choice elements is not present in the generated class. To work around this problem, do not use the group element in the choice element. Instead of using a group element in a choice element, add all the elements of the group element to the choice element.
View this KB Article...

XmlValidatingReader Ignores the Schema Nillable and the XML Nill Attributes
KB: 814177
When you validate an empty XML instance document by using XmlValidatingReader, you may receive the following error message:

Element 'ElementName' has incomplete content. Expected 'Employee'. An error occurred at file :///FileName.

Where ElementName is the name of an empty element, and where FileName is the name of the XML instance document. You receive the error message even though in the schema file, the element has the nillable attribute set to true, and has a complex content. Additionally, the empty element in the instance document has the nill attribute set to true. The XmlValidatingReader ignores the nillable and nill attributes, and throws the error.
View this KB Article...

ADO.NET Limitation in Validating XSD Facets
KB: 811107
ADO.NET does not throw any exceptions when it validates data that is newly inserted or modified in a DataRow. This is true if the DataRow violates XSD facets that are defined in an underlying XSD schema of the DataSet object. ADO.NET currently validates only the length and maxLength facets for the XSD string primitive data type. All other XSD facets are ignored by ADO.NET when it validates data that is newly inserted or modified in a DataRow. This is currently a known limitation in ADO.NET. You can work around this problem by using a System.Xml.XmlValidatingReader object to validate the XML representation of the data in a DataSet against its underlying schema.
View this KB Article...

Incorrect Results Occur When a Web Service Returns an Array of Size 0
KB: 330065
If you have a Web service that returns object arrays of size 0, the parameter is not deserialized correctly when the client receives the response. This problem occurs because deserializer does not deserialize the parameter correctly if the array is empty. To work around this problem use an end element for empty arrays.
View this KB Article...

Web Service Request Is Rejected When You Use a Header
KB: 330064
When you use a .NET client to talk to a non-.NET Web service, the server rejects the request. This occurs because a header element and a body element share the same href id attributes. This occurs when you call a remote procedure call (RPC) encoded Web service that accepts a header.
View this KB Article...

Use an MCMS Web Service to Import Multiple Items into the Resource Gallery
KB: 327750
You can use the Web Author to administer resource gallery items in Microsoft Content Management Server (MCMS) 2002. However, if you must add multiple items to the resource gallery, this may be inconvenient. This article describes how to create a MCMS Web service to perform bulk imports of resources into the resource gallery.
View this KB Article...

Compiler Error When You Use XmlAttribute
KB: 326706
When you compile a Visual J# .NET application that imports from both System.Xml and System.Xml.Serialization and that uses the attribute XmlAttribute, you receive the following compiler error message:

error VJS1397: Attribute 'System.Xml.XmlAttribute' doesn't inherit from 'System.Attribute'
View this KB Article...

XmlDataDocument Does Not Fire NodeChanged Events
KB: 326599
If an XmlDataDocument object is bound to a DataSet object, and the DataSet data is changed, the XmlDataDocument does not fire NodeChanged events.

When the XmlDataDocument object is bound to a DataSet object, the XmlDataDocument does not contain nodes. Nodes are created when they are first accessed. Because the XmlDataDocument does not yet contain nodes, changes to the DataSet do not trigger NodeChanged events.

To work around this problem, you must access each and every node in the document tree. To do this, use the InnerText property of the XmlDataDocument object one time. When each node has been accessed (and, therefore, created) all events fire.
View this KB Article...

Error Message When You Display Multi-Dimensional XML Data in the Visual Studio .NET XML Designer
KB: 325696
Valid XML documents that contain multi-dimensional data (for example, a single table that participates in more than one parent-child relationship) cannot be displayed in the Visual Studio .NET XML Designer Data view.

When you try to switch to Data view, you receive the following error message on the Data tab of the XML Designer:
Although this XML document is well formed, it contains structure that Data view cannot display. The same table (Table name) cannot be the child table in two nested relations.
View this KB Article...

Page: 1  2  3  

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