读取Excel文件作为一个服务器进程 [英] Reading Excel Files as a Server Process

问题描述

我试图找到一个合适的方式来读取NT操作系统的服务器上的Excel文件的内容。我使用Excel API许多问题，然后在对办公自动化的官方微软推出其中规定，Excel的API不适合Excel自动化。我看到的各种各样的问题是相似的文章中介绍。

I'm trying to find an appropriate way to read the contents of an Excel file on an NT server operating system. I have numerous problems using the Excel API and then came across the official Microsoft on Office Automation which states that the Excel API is not suitable for Excel automation. The sorts issues that I saw were similar to those described in the article.

有没有我可以在这样一个不遭受同样类型的线程/安全/许可问题，内征收的方式读取服务器（无UI）上的Excel文件（XLS，XLSX，XLSM）的另一种方式Excel的API？

Is there another way that I can read an Excel file (xls, xlsx, xlsm) on a server (no UI) in such a way that doesn't suffer the same sort of threading/security/license issues imposed within the Excel API?

推荐答案

有一个数字，是由不同的用户，将允许所需的排序功能凸显库。我在这里列举其中一些，这些评价让在适当情况下我试图放下有趣的评论比较他们。我已经包括的细节是完全基于意见，但任何一个库，可能会达到所要求的目标。

There were a number of libraries that were highlighted by different users that would allow the sort of functionality required. I've listed them here and some of these were evaluated so where appropriate I've tried to put down interesting comments for comparing them. The details I've included are completely opinion based, however any of these libraries would probably achieve the required goal.

US preadsheetGear.Net 结果
（没有评估，由于高购买成本）

SpreadsheetGear.Net
(Didn't evaluate due to high purchase cost)

<一个href=\"http://www.aspose.com/categories/file-format-components/aspose.cells-for-.net-and-java/default.aspx\">Aspose.Cells

（由collegue评估。眼看就要实现相当简单，性能堪比到Excel互操作）。

Aspose.Cells
(Evaluated by a collegue. Appeared to be fairly simple to implement, performance comparable to Excel Interop).

GemBox 结果
（未评估）

GemBox
(Didn't evaluate)

Excel服务结果
（好像只有被列入SharePoint 2007中）

Excel Services
(Seems only to be included in SharePoint 2007)

Excel的映射
 （没有评估，因为它需要强类型对象导入到其中并没有适合我的要求）。

Excel Mapper (Didn't evaluate because it requires strongly typed objects to import into which didn't fit my requirement).

SmartXls 结果
（没有评估，因为它需要强类型对象导入到其中并没有适合我的要求）。

SmartXls
(Didn't evaluate because it requires strongly typed objects to import into which didn't fit my requirement).

ActiveXls 结果
（相当容易使用，缺乏属性的提出问题，他们有方法的琐碎行动preference。尽管这是1M的索赔记录了第二次是从由廉价FLEXCEL执行。已经决定，帮助/ API手册几乎是没用的。）

ActiveXls
(Fairly easy to use, lack of Properties raises questions, they have a preference of Methods for trivial actions. Despite it's claim of 1M records a second was out performed by cheaper FlexCel. Have decided that the help/API manual is almost useless.)

Koogra 结果
（没有评估，由于发现没有单证/信息）

Koogra
(Didn't evaluate due to finding no documentations/information)

FileHelpers 结果
（未评估）

FileHelpers
(Didn't evaluate)

FLEXCEL 结果
（最低成本解决方案发现，良好的性能和简单用接近到Excel互操作的结构来实现。也收到从支持技术问题的快速反应。可能是我的一堆选秀权。）

SyncFusion的BackOffice 结果
（中等成本并有合理的结构。运行单元测试时，不幸的是有更多的困难，实施和不一致的结果。还获得了一些尝试读取受保护的内存错误，不鼓励我，纯粹的托管库）。

SyncFusion BackOffice
(Medium cost and had a reasonable structure. Unfortunately had more difficulty implementing and inconsistent results when running unit tests. Also received a number of 'Attempted to read protected memory' errors, which didn't encourage me with purely managed library.)

这篇关于读取Excel文件作为一个服务器进程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！