title: Issue with NumberFormat in ExportAsFixedFormat
body: <p>I have a table of data (calculation results) that the user should be able to export to different formats. I use <code>Interop.Excel</code> to prepare a table with the data and use the data and format it using visual formatting (fonts, colors etc.) and <code>NumberFormat</code>. Example:</p>
  
  <pre><code>cellRange.NumberFormat = "#,##0";
  </code></pre>
  
  <p>When I save the table as an <strong>Excel</strong> file all formatting is ok when exporting to <strong>.xlsx</strong> and <strong>.xls</strong>:</p>
  
  <pre><code>excelWorkBook.SaveAs(exportFileName, Excel.XlFileFormat.xlOpenXMLWorkbook); // for .xlsx
  excelWorkBook.SaveAs(exportFileName, Excel.XlFileFormat.xlExcel8); // for .xls
  </code></pre>
  
  <p>I also want to give the user the possibility to export this table to <strong>.pdf</strong> and <strong>.xps</strong> from the application without having to open the Excel file. As I have prepared the tables in <code>Interop.Excel</code>, I tried exporting the same table to those file formats:</p>
  
  <pre><code>excelWorkBook.ExportAsFixedFormat(Excel.XlFixedFormatType.xlTypePDF,exportFileName); // for .pdf
  excelWorkBook.ExportAsFixedFormat(Excel.XlFixedFormatType.xlTypeXPS,exportFileName); // for .xps
  </code></pre>
  
  <p>Both of these result in good documents except that all <code>NumberFormats</code> are lost resulting in long decimal values of doubles. This is not appropriate for the customer's summary of the data. (Colors and fonts remain as defined in <strong>.pdf</strong> and <strong>.xps</strong>.)</p>
  
  <p>I have tried setting <code>.Style</code>and <code>.Styles</code> to <code>"Number"</code> or the like. This does not solve the problem.</p>
  
  <p>I have also tried to protect the <code>Range</code> of cells or the <code>excelWorkSheet</code>. This does not solve the problem either.</p>
  
  <p>Someone suggested calling a <strong>VBA macro / sub</strong> through <strong>C#</strong> but after some looking into that, I get the impression that it's not a very straight forward (or stable) path.</p>
  
  <p>I am looking for any help in resolving this issue through <code>Interop.Excel</code> or in another way.</p>
  
  <p>lucn</p>