There a couple of files that are added to the AddIn setup package by
default...
Extensibility.dll, VSLangProj.dll, and vslangproj.tlb.
Why? If you are creating an AddIn for Visual Studio, those are already
installed on the client computers...otherwise, they would not be able to run
VS .. or macro's....so, why are they included?
The reaoson I am asking is...when you install/uninstall for debugging
purposes...occasionally during the uninstall, the uninstaller unregisters
VSLangProj.dll and Extensibility.dll ... therefore, you can't add classes to
existing projects or use any other type of wizard because they use the
Extensibility.dll and VSLangProj.dll assemblies....
bug?
Thanks,
Mythran
Carlos J. Quintero [VB MVP] - 09 Jan 2006 10:34 GMT
Hi Mythran
Yes, it is a known bug. I discussed it with some people from MS and they
acknowledged the issue. See:
http://blogs.msdn.com/jim_glass/archive/2005/08/18/453218.aspx

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio 2005, Visual Studio .NET,
VB6, VB5 and VBA
You can code, design and document much faster in VB.NET, C#, C++ or VJ#
Free resources for add-in developers:
http://www.mztools.com
> There a couple of files that are added to the AddIn setup package by
> default...
[quoted text clipped - 15 lines]
> Thanks,
> Mythran
Mythran - 09 Jan 2006 16:40 GMT
> Hi Mythran
>
[quoted text clipped - 22 lines]
>> Thanks,
>> Mythran
kk, thanks ;)
Mythran
Mirko Matytschak - 10 Jan 2006 16:42 GMT
Hi Mythran,
exclude these dlls from your installer project (Under "Detected
Dependencies" right click on these dlls and choose "Exclude"). So they won't
get uninstalled, if you uninstall your add-in.
Mirko
> There a couple of files that are added to the AddIn setup package by
> default...
[quoted text clipped - 15 lines]
> Thanks,
> Mythran