

For example, the configuration attributes Name, arm_architecture etc are on their own lines:

But a worse problem is that the original project file uses a mixture of attribute each on their own line and in-line attributes, which the. Using the replaced DOCTYPE leaves a space after the CrossStudio_Project_File but SES copes with this, and is a minor cosmetic effect. Parent.ReplaceChild(n.CreateDocumentType("CrossStudio_Project_File", Nothing, Nothing, Nothing), n.DocumentType) '4th param in CreateDocumentType has to be Nothing to avoid getting in DOCTYPE, which is what you get by default and with empty string Dim n As XmlDocument = New XmlDocument()ĭim parent As XmlNode = n.DocumentType.ParentNode The workaround is to create a new XML Document object and replace the Document Type with a new one, with Nothing (in VB.NET, equivalent to null in C#) for the subset object, as distinct from an empty string. NET framework, so you get which although is valid XML, causes SES to say that the file is not a valid project.

The DOCTYPE tag changes in that additional square brackets appear at the end due to a bug in the. However, writing out an this XML document object back to a file has a few problems. Once the XML is loaded, an attribute such as c_user_include_directories can be read using this syntax sIncludes = Writing In VB.NET, Private xmlDoc As XmlDocument = New XmlDocument() Segger Embedded Studio project files appear to be XML formatted with a custom DOCTYPE.
