XML CDATA Literal (Visual Basic)
Updated: July 20, 2015
For the latest documentation on Visual Studio 2017, see Visual Studio 2017 Documentation.
A literal representing an XCData object.
Required. Denotes the start of the XML CDATA section.
Required. Text content to appear in the XML CDATA section.
Required. Denotes the end of the section.
An XCData object.
XML CDATA sections contain raw text that should be included, but not parsed, with the XML that contains it. A XML CDATA section can contain any text. This includes reserved XML characters. The XML CDATA section ends with the sequence "]]>". This implies the following points:
You cannot use an embedded expression in an XML CDATA literal because the embedded expression delimiters are valid XML CDATA content.
XML CDATA sections cannot be nested, because
contentcannot contain the value "]]>".
You can assign an XML CDATA literal to a variable, or include it in an XML element literal.
An XML literal can span multiple lines but does not use line continuation characters. This enables you to copy content from an XML document and paste it directly into a Visual Basic program.
The Visual Basic compiler converts the XML CDATA literal to a call to the XCData constructor.
The following example creates a CDATA section that contains the text "Can contain literal <XML> tags".