VSTO vs Excel-DNA的优点和缺点？ [英] Pros and cons of VSTO vs Excel-DNA?

问题描述

据了解，VSTO和Excel-DNA提供了将.NET代码导入Excel的两种不同解决方案。一个解决方案是开源的，另一个解决方案是由Microsoft开发的。每个解决方案的优缺点是今天和未来？

As far as I understand VSTO and Excel-DNA offer two different solutions for getting .NET code into Excel. One solution is open-source and the other solution is developed by Microsoft. What are the pros and cons of each solution, today and going forward?

推荐答案

VSTO

+适合大规模团队发展

+如果您已经有Visual Studio Pro，它的免费

+适用于COM插件和UI开发

+ Microsoft产品

- .NET-Interop的性能很差

- 仍然难以处理多个Excel版本

- VBA用户的显着学习曲线

- 无UDF支持

VSTO
+ is suitable for large-scale team development
+ If you already have Visual Studio Pro its free
+ good for COM addins & UI development
+ Microsoft product
- performance of .NET-Interop is poor
- Still difficult to handle multiple Excel versions
- significant learning curve for VBA user
- no UDF support

Excel DNA

+优秀的UDF性能（ XLL-.NET）

+支持COM - Interop和XLL接口

+易于使用和部署

+使用或不使用Visual Studio

+免费和开放源码

- 没有文档记录，但优秀的支持小组

Excel DNA
+ Excellent UDF performance (XLL-.NET)
+ suports both the COM - Interop and the XLL interfaces
+ easy to use and deploy
+ use with or without Visual Studio
+ Free and open source
- Not well documented but excellent support group

您还应该考虑Addin Express，像Excel的DNA，支持COM接口和XLL接口，并有许多向导来构建东西。但它的开源并不是免费的。

You should also consider Addin Express which, like Excel DNA, supports both the COM interface and the XLL interface and has many wizards for building things. But its not open source and its not free.

这篇关于VSTO vs Excel-DNA的优点和缺点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！