Add-in vs VSIP package

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

noob - 21 Nov 2007 18:55 GMT

Hi all,

I'm new to writing add-ins and plug-ins in general.

Currently I'm trying to develop a small app that can be docked inside
VS2005, written in C# .NET2.0.

First of all, what is the difference between the regular Visual Studio
Add-in vs the VSIP package?

Can I achieve the same thing with both? It looks like the VS add-in is
simpler..

Thanks in advance.

Reply to this Message

Richard - 21 Nov 2007 21:10 GMT

[Please do not mail me a copy of your followup]

=?Utf-8?B?bm9vYg==?= <noob@discussions.microsoft.com> spake the secret code
<3B2C51CF-2CEC-4293-BDDB-4229EAAF5947@microsoft.com> thusly:

>Can I achieve the same thing with both? It looks like the VS add-in is
>simpler..

Most things can be done with an add-in (and yes, its simpler).

You can't add new languages with an add-in however. For that, you
must go the VSIP route.

Signature

"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>

Legalize Adulthood! <http://blogs.xmission.com/legalize/>

Reply to this Message

Darren Stokes - 05 Dec 2007 23:33 GMT

If you app is something that works along side the existing project types,
then an add-in is the way to go. Like Richard said in his reply, plug-ins
are for deeper integration with Visual Studio. Creating your own project
types, languages, debuggers, etc.

Add-ins work with Visual Studio's COM automation capability and plug-ins
work with the VS.net SDK, which is considerably more complicated. Most of
the products you will see are actually add-ins.

> Hi all,
>
[quoted text clipped - 10 lines]
>
> Thanks in advance.

Reply to this Message

Add-in vs VSIP package

Free Magazines