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

问题描述

我试图找到一种适当的方法来读取NT服务器操作系统上的Excel文件的内容。我使用Excel API有许多问题，然后遇到官方的 Microsoft on Office Automation 其中指出，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.

有另一种方法可以读取Excel文件（xls，xlsx，xlsm）服务器（没有UI），不会受到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.

SpreadsheetGear.Net

（由于购买费用较高而没有评估）

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

Aspose.Cells

（由同事评估，看起来相当简单，实现性能与Excel Interop相当）。

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

GemBox

（未评估）

GemBox
(Didn't evaluate)

Excel Services

（似乎只能包含在SharePoint 2007中）

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

Exc el Mapper
（没有评估，因为它需要导入的强类型对象不符合我的要求）。

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 < a>

（相当容易使用，缺少属性引发问题，他们偏爱方法进行微不足道的操作。尽管拥有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 Interop结构紧密相连，并从支持中快速回复技术问题。可能是我的选择。）

SyncFusion BackOffice

（中等成本合理，结构合理，不幸的是，当r单元测试。还收到了一些尝试读取受保护的内存错误，这并不鼓励我使用纯管理的库。）

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屋！