Cannot compile latest version sourcecode (rev27264)

Nov 23, 2009 at 8:18 PM
Edited Nov 23, 2009 at 8:20 PM

Hello,

I tried to compile the sourcecode, but it failed. Initial the Excel project compiles, but the Excel.Tests didn't (missing Factory and ExcelFileType).  Then I saw that the project file was missing some files (they were in the folder but not in the .csproj files). This counts for the Excel and also the Excel.Tests project. So then I included all the other files in the project, but now I get the errors:

Error    1    'Excel.Core.BinaryFormat.XlsWorksheet' does not contain a definition for 'Data' and no extension method 'Data' accepting a first argument of type 'Excel.Core.BinaryFormat.XlsWorksheet' could be found (are you missing a using directive or an assembly reference?)    ...\exceldatareader-27264\Excel\ExcelDataReader.cs    152    45    Excel

Error    2    'Excel.Core.BinaryFormat.XlsWorksheet' does not contain a definition for 'Data' and no extension method 'Data' accepting a first argument of type 'Excel.Core.BinaryFormat.XlsWorksheet' could be found (are you missing a using directive or an assembly reference?)    ...\exceldatareader-27264\Excel\ExcelDataReader.cs    306    10    Excel

So more in detail: error 2

It calls in ExcelDataReader.cs:

private bool ReadWorksheet(XlsWorksheet sheet) { 
...
sheet.Data = dt;
...
}

But XlsWorksheet has no Data property. So do I compile some old codefiles? Are the csproj files out-to-date? Are the code-files out-of-sync?

Mar 30, 2010 at 10:25 AM
Not sure what the sync status of the source download is. However, removing the ExcelDataReaderTest and ExcelDataReader from the projects makes everything build. It looks like ExcelDataReader has been replaced by IExcelDataReader and its implementors.
May 20, 2010 at 9:55 PM
Hi, I just updated to v48578 and all tests seem broken, not just those in ExcelDataReaderTest. All 3 ...Test.cs files have references to the old 'Factory' class, which seems to have been replaced by ExcelReaderFactory. Can you confirm this? Is there going to be an update to the tests to address this issue? Thanks!