A couple of weeks ago I wrote about XML Namespace issues in VB: one in particular was to do with namespace declarations being repeated in the output X ML. In those cases we only looked at common namespaces for the entire document. However the example of creating a word document I posted earlier today...
If you programmatically add attributes with namespaces to an XElement, when the XElement is written out it will give each attribute a namespace prefix and then define a xmlns for that prefix. The way XElement does this is first it examines the namespaces already active and also those defined in the element...
If you use XML literals in your code, adding one to another: Dim e1 = <a:books></a:books> dim e2 = <a:book></a:book> e1.Add(e2) You will have the xmlns declaration repeated in each of the elements, when really it is only needed once per the document or outer element. The problem...
Posted to
@ Head
(Weblog)
by
bill
on
11-24-2007
Filed under: VB, Orcas, LINQ, VSM, DevCenter, Bug
In VB9, there's a bug when using XML literals with any type member that is a protected keyword. For example, given the following psuedo types, Class Doc Public Property [Imports]() As List( Of DocImports) End Class Class DocImports Public Property [Namespace]() As String End Class The following code...
Posted to
@ Head
(Weblog)
by
bill
on
11-20-2007
Filed under: VB, Orcas, LINQ, DevCenter, VS2008, Bug