hockie53

I have created an addin for VS05 profession edition that will automatically gac and register all projects in a solution that require it. The addin works correctly on the dev machine but when i try to give to any other developers it will not work.

I have been sending them the .addin and the project .dll files and having them place them in the Addins folder. The addin will not even appear in the addin manager. Any suggestions



Re: Visual Studio Extensibility VS2005 Addin Deployment

Karstman

I create my own directory in Program Files and put my .addin and .dll in it.
For the Assembly tag in the .addin file I reference the local .dll file:

<Assembly>assemblyName.dll</Assembly>


Then either add the folder path to the "Add-in File Paths" manually through Visual Studio>>Options>>Add-in/Macro Security

or add the path through code to the following reg key (for all users):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\AutomationOptions\LookInFolders

or this one for current user:

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\AutomationOptions\LookInFolders




Re: Visual Studio Extensibility VS2005 Addin Deployment

hockie53

Thanks, this is working for some of our computers but some will not show the the add-in in addin manager whatsoever. It seems like VS is not even trying to look there. I have added the path to the addin folder and even edited the reg key. Is there any known bugs as both the problem computers have just upgraded to SP1 for VS 2005. Also is there any way a project reference could be affecting this. There is one project reference Interop.COMAdmin.dll
that was set to copy local so I have also included it in the add-in directory. I would think a reference problem would affect the add-in working but not weather or not it appears in the add-in manager. Any thoughts




Re: Visual Studio Extensibility VS2005 Addin Deployment

Karstman

I know I originally tried it by registering the assembly in the GAC and that did not work for me, so I stopped that, then it would find it in the location I specified to "LookIn"

Do you mind posting the contents of the .addin file





Re: Visual Studio Extensibility VS2005 Addin Deployment

hockie53

This is the contents of the .addin file:

< xml version="1.0" encoding="UTF-16" standalone="no" >
<Extensibility xmlns="http://schemas.microsoft.com/AutomationExtensibility">
<HostApplication>
<Name>Microsoft Visual Studio</Name>
<Version>8.0</Version>
</HostApplication>
<Addin>
<FriendlyName>GacReg</FriendlyName>
<Description>GacReg</Description>
<Assembly>GacReg.dll</Assembly>
<FullClassName>GacReg.Connect</FullClassName>
<LoadBehavior>1</LoadBehavior>
<CommandPreload>1</CommandPreload>
<CommandLineSafe>0</CommandLineSafe>
</Addin>
</Extensibility>





Re: Visual Studio Extensibility VS2005 Addin Deployment

Karstman

Just to be clear...

The .addin file is in the same location as GacReg.dll like such:

c:\SomeFolder\Foo\GacReg.AddIn

c:\SomeFolder\Foo\GacReg.dll

Then you added "C:\SomeFolder\Foo" in the registry key below

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\AutomationOptions\LookInFolders

After adding that reg key, does the path show in Visual Studio under Tools>>Options>>Add-in/Macro Security, in the Add-in File Paths

if you add directly into that list via the IDE, I am pretty sure it rights the path to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\AutomationOptions\LookInFolders





Re: Visual Studio Extensibility VS2005 Addin Deployment

hockie53

Yes that is all correct, this is why we are so stumped. I even took the .addin and .dll home and they worked instantly my home machine. I guess it has to be somthing with the VS setup on their machines.

The files are in the same Dir.

The reg key is added here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\AutomationOptions\LookInFolders

The path appears in VS under tools>>options>>addin/macro security & still it does not pick them up.

I even tryed to remove the dll and leave the addin file so that it would throw the error that the dll could not be found and nothing, so thats why i think that it is still not even tryin to load the addin for whatever reason. Thank you for your help so far it is much appreciated.