jmac82

I've created an Excel 2007 Add-in. in visual studio 2005 / VSTO 2005 SE.
When i run the setup application, it installs and work perfectly on my
development machine.

I followed the "
Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer" article

When i install in on a users machine, it installs with success, and all
the registry-settings are identical as the ones on my Development machine. But the add-in does'nt show (i created a custom ribbon-tab)

The only difference i see on the users machine is, in Excel 2007.
When i open Excel Options->Add-Ins My add-in appears in the list, under
Active Application Extensions..
But when i select my add-in in the list, the location displayed in the information-area under the list, is not the location of my add-in, but "C:\programfiles\ ... \Microsoft Shared\VSTO\8.0\AddinLoader.dll

Compared to my developmentmachine, "C:\programfiles\myApp\myaddin.dll.manifest


Re: Visual Studio Tools for Office Addin does'nt show

Dennis Wallentin

Hi,


The AddinLoader.dll is responsible for loading the add-in in its own AppDomain (and isolating it from the other .NET add-ins). This is how it should work so at least this part is not an issue. I suspect it's related to the CAS which You can read more about in the links I provide here.






Re: Visual Studio Tools for Office Addin does'nt show

Andrew Cherry [MSFT]

Hi -

What you're seeing on your development machine is the correct location in Office 2007. If you're seeing AddinLoader.dll, I'm wondering where your registry entries are placed on your user machine.

The only registry entries that should need to be written are:

HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\{YourAddInName}

\LoadBehavior=3

\Manifest={ManifestPath}

...

Please note, it should not be installed into HKEY_LOCAL_MACHINE.

The only way the AddinLoader.dll could be populated in that box is if Office does not know it's a managed add-in. If either the Manifest key is missing, or the registration is in HKLM (the Manifest key would still need to be absent), it would still be insufficient -- values under HKCR would need to be written to map the {YourAddInName} to a CLSID, and then the CLSID to an InprocServer32.

If nothing appears to be the problem, please post the actual registry values you're writing, and we might be able to point out a detail you may have missed.

Hope this helps,

Andrew





Re: Visual Studio Tools for Office Addin does'nt show

jmac82

I double checked that everything in the registry etc. was identical to the settings on my development machine. And since the add-in was under the "Active Application Extensions" category in Excels settings, i guessed that the CAS wasn't the problem.

So i tried to install my add-in on my home computer, and it worked perfectly. I also tried to install it on a third computer, with a clean Excel installed.. Also here it worked perfectly. So I guess something wasn't right on the testing computer I tried the first time.

Thanks for your responses.




Re: Visual Studio Tools for Office Addin does'nt show

jmac82

Dennis Wallentin wrote:

Hi,


The AddinLoader.dll is responsible for loading the add-in in its own AppDomain (and isolating it from the other .NET add-ins). This is how it should work so at least this part is not an issue. I suspect it's related to the CAS which You can read more about in the links I provide here.



I am a novice to Add-in development.
But since the AddinLoader.dll is "responsible for loading the add-in in its own AppDomain (and isolating it from the other .NET add-ins)" does this mean that shimming is not an issue then As I understand, based on what I've read, this is the reason to shim my add-in