使用非 VBA 语言开发 MSFT Office 宏的当前技术水平如何？
很久以前，为 MSFT Office 编写 VBA 宏是我工作的一部分。
现在看来我可能会再次走上这条路，而且我已经很多年没有碰过 MSFT Office 做过任何严肃的事情了。
VBA 仍然是创建 msft Office 扩展的事实上的标准吗？
是否可以用除 VBA 之外的任何语言编写（非二等公民）MSFT Office 扩展？
Long ago writing VBA macros for MSFT Office was part of my job.
Now it looks like I may be traveling down that road again, and I have not touched MSFT Office for anything serious in years.
Is VBA still the de-facto standard for creating msft office extensions?
Is it possible to write (non-second-class-citizen) MSFT office extensions in any language besides VBA yet?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
宏对于原型设计仍然很有用。然而，由于它们是恶意代码的简单攻击媒介，我会尽量避免广泛使用它们。您是否考虑将 Visual Studio Tools for Office 作为一个平台？
Macros are still good for prototyping. However, since they are an easy attack vector for malicious code I would try to avoid them for wide use. Have you consider Visual Studio Tools for Office as a platform?
“最先进的”是使用 .NET 语言进行 Office 开发，使用 VSTO。这通常通过 C# 或 VB.NET 完成。
The "state of the art" is to use a .NET language for Office development, using VSTO. This is typically done via C# or VB.NET.
我对此的看法是集成 VSTO 和 IronPython。我们已经用这个组合制定了多个解决方案，并且对此非常满意。它使您能够用 C# 编写解决方案的核心部分，同时拥有灵活的环境来自定义您的应用程序。
My take on this would be to integrate VSTO and IronPython. We have made several solutions with this combo and are very happy with it. It enables you to write core parts of your solution in C#, but at the same time have a flexible environment to customize your application.