“Visual Studio Integration Package” vs “Visual Studio Add-in”: what is the difference?
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?
visual-studio vsx visual-studio-addins vspackage
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
add a comment |
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?
visual-studio vsx visual-studio-addins vspackage
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
add a comment |
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?
visual-studio vsx visual-studio-addins vspackage
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
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?
visual-studio vsx visual-studio-addins vspackage
visual-studio vsx visual-studio-addins vspackage
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
edited Jul 14 '11 at 21:18
Kate Gregory
17.5k74881
17.5k74881
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
asked Jul 16 '09 at 18:07
Nathan VoxlandNathan Voxland
10.6k13349
10.6k13349
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Ok, you can find a full detailed comparison here (there are also links to the previous parts in the series).
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.
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.
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
- you need access to high-level extensibility API, as opposed to low-level fundamental API available from a VS package;
- you develop in Visual Basic (templates for VS Package are available only in C# / Visual C++);
- you want to automate a simple task / common scenario, then add-in will probably require less development effort.
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
add a comment |
Important point on Visual Studio Add-in vs Package, Add-ins are deprecated in VS 2013 and will not be available in VS "14"
Add-ins Deprecated in Visual Studio 2013
Visual Studio "14" CTP: add-ins are gone
"Official" guidance from How to: Create an Add-In is "Visual Studio add-ins are deprecated in Visual Studio 2013. You should upgrade your add-ins to VSPackage extensions...."
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
add a comment |
An integration package is something that can be chosen when you start a new project (like how you pick C# or VB).
See http://www.bitwisemag.com/copy/features/dev/visual_studio/vs2005_integration_1.html.
Add-ins work just like they would for MS Office applications. You can add your own custom buttons and menu items. Here is an example: http://www.c-sharpcorner.com/UploadFile/mgold/AddIns11292005015631AM/AddIns.aspx.
answered Jul 16 '09 at 18:26
NelsonNelson
426410
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f1139294%2fvisual-studio-integration-package-vs-visual-studio-add-in-what-is-the-diffe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ok, you can find a full detailed comparison here (there are also links to the previous parts in the series).
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.
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.
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
- you need access to high-level extensibility API, as opposed to low-level fundamental API available from a VS package;
- you develop in Visual Basic (templates for VS Package are available only in C# / Visual C++);
- you want to automate a simple task / common scenario, then add-in will probably require less development effort.
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
add a comment |
Ok, you can find a full detailed comparison here (there are also links to the previous parts in the series).
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.
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.
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
- you need access to high-level extensibility API, as opposed to low-level fundamental API available from a VS package;
- you develop in Visual Basic (templates for VS Package are available only in C# / Visual C++);
- you want to automate a simple task / common scenario, then add-in will probably require less development effort.
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
add a comment |
Ok, you can find a full detailed comparison here (there are also links to the previous parts in the series).
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.
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.
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
- you need access to high-level extensibility API, as opposed to low-level fundamental API available from a VS package;
- you develop in Visual Basic (templates for VS Package are available only in C# / Visual C++);
- you want to automate a simple task / common scenario, then add-in will probably require less development effort.
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
Ok, you can find a full detailed comparison here (there are also links to the previous parts in the series).
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.
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.
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
- you need access to high-level extensibility API, as opposed to low-level fundamental API available from a VS package;
- you develop in Visual Basic (templates for VS Package are available only in C# / Visual C++);
- you want to automate a simple task / common scenario, then add-in will probably require less development effort.
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
edited Apr 10 '14 at 20:15
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
answered Jan 13 '10 at 19:36
Max GalkinMax Galkin
13.9k957107
13.9k957107
add a comment |
add a comment |
Important point on Visual Studio Add-in vs Package, Add-ins are deprecated in VS 2013 and will not be available in VS "14"
Add-ins Deprecated in Visual Studio 2013
Visual Studio "14" CTP: add-ins are gone
"Official" guidance from How to: Create an Add-In is "Visual Studio add-ins are deprecated in Visual Studio 2013. You should upgrade your add-ins to VSPackage extensions...."
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
add a comment |
Important point on Visual Studio Add-in vs Package, Add-ins are deprecated in VS 2013 and will not be available in VS "14"
Add-ins Deprecated in Visual Studio 2013
Visual Studio "14" CTP: add-ins are gone
"Official" guidance from How to: Create an Add-In is "Visual Studio add-ins are deprecated in Visual Studio 2013. You should upgrade your add-ins to VSPackage extensions...."
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
add a comment |
Important point on Visual Studio Add-in vs Package, Add-ins are deprecated in VS 2013 and will not be available in VS "14"
Add-ins Deprecated in Visual Studio 2013
Visual Studio "14" CTP: add-ins are gone
"Official" guidance from How to: Create an Add-In is "Visual Studio add-ins are deprecated in Visual Studio 2013. You should upgrade your add-ins to VSPackage extensions...."
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
Important point on Visual Studio Add-in vs Package, Add-ins are deprecated in VS 2013 and will not be available in VS "14"
Add-ins Deprecated in Visual Studio 2013
Visual Studio "14" CTP: add-ins are gone
"Official" guidance from How to: Create an Add-In is "Visual Studio add-ins are deprecated in Visual Studio 2013. You should upgrade your add-ins to VSPackage extensions...."
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
edited Nov 21 '18 at 11:29
Vincent Vancalbergh
2,88221724
2,88221724
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
answered Sep 25 '14 at 16:49
Greg DuncanGreg Duncan
25623
25623
add a comment |
add a comment |
An integration package is something that can be chosen when you start a new project (like how you pick C# or VB).
See http://www.bitwisemag.com/copy/features/dev/visual_studio/vs2005_integration_1.html.
Add-ins work just like they would for MS Office applications. You can add your own custom buttons and menu items. Here is an example: http://www.c-sharpcorner.com/UploadFile/mgold/AddIns11292005015631AM/AddIns.aspx.
answered Jul 16 '09 at 18:26
NelsonNelson
426410
add a comment |
An integration package is something that can be chosen when you start a new project (like how you pick C# or VB).
See http://www.bitwisemag.com/copy/features/dev/visual_studio/vs2005_integration_1.html.
Add-ins work just like they would for MS Office applications. You can add your own custom buttons and menu items. Here is an example: http://www.c-sharpcorner.com/UploadFile/mgold/AddIns11292005015631AM/AddIns.aspx.
answered Jul 16 '09 at 18:26
NelsonNelson
426410
add a comment |
An integration package is something that can be chosen when you start a new project (like how you pick C# or VB).
See http://www.bitwisemag.com/copy/features/dev/visual_studio/vs2005_integration_1.html.
Add-ins work just like they would for MS Office applications. You can add your own custom buttons and menu items. Here is an example: http://www.c-sharpcorner.com/UploadFile/mgold/AddIns11292005015631AM/AddIns.aspx.
answered Jul 16 '09 at 18:26
NelsonNelson
426410
An integration package is something that can be chosen when you start a new project (like how you pick C# or VB).
See http://www.bitwisemag.com/copy/features/dev/visual_studio/vs2005_integration_1.html.
Add-ins work just like they would for MS Office applications. You can add your own custom buttons and menu items. Here is an example: http://www.c-sharpcorner.com/UploadFile/mgold/AddIns11292005015631AM/AddIns.aspx.
answered Jul 16 '09 at 18:26
NelsonNelson
426410
answered Jul 16 '09 at 18:26
NelsonNelson
426410
answered Jul 16 '09 at 18:26
NelsonNelson
426410
answered Jul 16 '09 at 18:26
NelsonNelson
426410
426410
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f1139294%2fvisual-studio-integration-package-vs-visual-studio-add-in-what-is-the-diffe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
