"Visual Studio集成包"对比"Visual Studio加载项":有什么区别? [英] "Visual Studio Integration Package" vs "Visual Studio Add-in": what is the difference?

问题描述

为Visual Studio创建新扩展时，有两个项目选项:"Visual Studio集成包"和"Visual Studio加载项".两种项目类型有什么区别?什么时候可以使用另一种?

When creating a new extension for visual studio, there are two project options: "Visual Studio Integration Package" and "Visual Studio Add-in". What is the difference between the two project types and when would you use one over the other?

推荐答案

好，您可以找到此处有完整的详细比较(也有指向本系列前面各部分的链接).

Ok, you can find a full detailed comparison here (there are also links to the previous parts in the series).

但是，基本上，从VS的第一个版本开始，插件就可以作为VS扩展类型使用，并作为COM组件构建.后来，在这种方法中发现了一些局限性，因此创建了新的可扩展性功能-VS SDK程序包.

But basically, add-ins were available as the VS extension type from the very first versions of the VS and built as the COM components. Later on, some limitations were discovered in that approach, so the new extensibility feature was created -- namely VS SDK package.

也许，如果您要为VS 2008+构建扩展，则应将VS SDK软件包定位为较新的技术. VS包的另一个优点是可以更好地与Visual Studio集成.

Probably, if you are building an extension for VS 2008+ you should target the VS SDK package as the newer technology. Another strong point of the VS package is better integration with the Visual Studio.

无论您做什么，加载项都是 Visual Studio的外部事物，而 VSPackages是完全集成的 IDE的一部分.

Whatever you do, add-ins are an external thing for Visual Studio while VSPackages are a completely integrated part of the IDE.

如果仍然可以，您仍可以考虑构建加载项

You still might consider building an add-in, if

• 您需要访问高级可扩展性API，而不是VS软件包中提供的低级基本API；
• 您在Visual Basic中开发(VS包模板仅在C#/Visual C ++中可用)；
• 您想自动化一个简单的任务/常见场景，那么外接程序可能需要较少的开发工作.

这篇关于"Visual Studio集成包"对比"Visual Studio加载项":有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！