The file uses ANSI encoding like all the other files.
Ah-Ha!!!! It seems the problem is because the file is in MS Excel XML
format. CC.Net seems not to like the namespaces it is trying to pull
in.
The file looks like:
<?xml version="1.0"?>
<?mso-application progid="Excel.Sheet"?>
<Workbook xmlns="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:x="urn:schemas-microsoft-com:office:excel"
>
<ExcelWorkbook xmlns="urn:schemas-microsoft-com:office:excel">
</ExcelWorkbook>
<Styles>
<Style ss:ID="s64">
<NumberFormat ss:Format="yyyy\-mm\-dd\ hh:mm:ss.000"/>
</Style>
<Style ss:ID="s65">
<NumberFormat ss:Format="hh:mm:ss.000"/>
</Style>
</Styles>
<Worksheet ss:Name="Sheet1">
<Table>
<Column/>
<Column/>
<Row>
<Cell><Data ss:Type="String">DATE</Data></Cell>
<Cell><Data ss:Type="String">FILE</Data></Cell>
</Row>
<Row>
<Cell ss:StyleID="s64"><Data
ss:Type="DateTime">2009-05-01T05:52:11</Data></Cell>
<Cell><Data ss:Type="String">//depot/path/path/filename.c</Data></
Cell>
</Row>
.
.
.
</Table>
</Worksheet>
</Workbook>
If I change this to:
<?xml version="1.0"?>
<?mso-application progid="Excel.Sheet"?>
<Workbook >
<ExcelWorkbook xmlns="urn:schemas-microsoft-com:office:excel">
</ExcelWorkbook>
<Styles>
<Style ID="s64">
<NumberFormat Format="yyyy\-mm\-dd\ hh:mm:ss.000"/>
</Style>
<Style ID="s65">
<NumberFormat Format="hh:mm:ss.000"/>
</Style>
</Styles>
<Worksheet Name="Sheet1">
<Table>
<Column/>
<Column/>
<Row>
<Cell><Data ss:Type="String">DATE</Data></Cell>
<Cell><Data ss:Type="String">FILE</Data></Cell>
</Row>
<Row>
<Cell StyleID="s64"><Data ss:Type="DateTime">2009-05-01T05:52:11</
Data></Cell>
<Cell><Data Type="String">//depot/path/path/filename.c</Data></
Cell>
</Row>
.
.
.
</Table>
</Worksheet>
</Workbook>
NOTE: the dropped namespaces and 'ss:' it merges correctly. :)
Looks like I will have to pre-process the file with a bit of magic
python code ;)
On 12 June, 11:18, Ruben Willems <[email protected]> wrote:
> Hi
>
> can you check the encoding of that file,
> maybe it is different from other xml files
>
> with kind regards
> Ruben Willems
>
> On Fri, Jun 12, 2009 at 12:16 PM,
>
> CinnamonDonkey<[email protected]> wrote:
>
> > Hi All,
>
> > I have a strange problem with the merge publisher.
>
> > One of our tasks generates a .xml file which I am trying to merge into
> > the build log and then later parse and render via XSL. Unfortunately
> > it seems that CC.Net always insists on merging this particular .xml
> > file wrapped in a CDATA section. This means that the XSL code can't
> > actually see any of the elements in the XML file. :(
>
> > Does anyone have any idea why this might be happening?
>
> > I do this a lot and haven't come across this problem with any other
> > xml files.
>
> > Cheers,
> > Shaun
