[英]VSTO vs. Primary Interop Assemblies, what's the difference?
I already developed a large Office application-level add-in and it works like a charm, but I have problems understanding the technical basis. 我已经开发了一个大型的Office应用程序级加载项,它就像一个魅力,但我在理解技术基础时遇到了问题。
VSTO is the application runtime that provides hooks ( solution loader ) into the Office subsystem via PIA. VSTO是应用程序运行时 ,它通过PIA向Office子系统提供挂钩( 解决方案加载器 )。 PIAs are wrappers around the unmanaged COM API (
IDTExtensibility2
) that Office is built from. PIA是围绕构建Office的非托管COM API(
IDTExtensibility2
)的包装器 。 PIAs provide managed access and run above the VSTO runtime. PIA提供托管访问并在VSTO运行时之上运行。
VSTO comes with project types that build the deployment manifest required for detecting dependencies and loading your Add-In at runtime. VSTO附带了项目类型,这些类型构建了在运行时检测依赖关系和加载加载项所需的部署清单 。
The PIAs provide managed access to the COM object-model, but it also supports unmanaged access should you want more control over how your solution is loaded ( hence you always have VSTO runtime, but not always PIAs ). PIA提供对COM对象模型的托管访问 ,但如果您希望更好地控制解决方案的加载方式,它还支持非托管访问 ( 因此您始终拥有VSTO运行时,但不总是PIA )。
This MSDN link provides a great overview of the evolution of PIAs and VSTO away from IDtExtensibility2
which is another loading option ( outside of PIAs ) 这个MSDN链接提供了远离
IDtExtensibility2
的PIA和VSTO演变的概述, IDtExtensibility2
是另一个加载选项( 在PIA之外 )
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.