I have an add-in 10 Studio in AppSource.
The current version (on 08/22/2019) is 1.5.1.0. We load well this version in Excel for Windows:
However, when we load the same add-in from the add-in Store in Excel for Mac, it returns the version 1.3.0.0.
It seems that the old version in Excel for Mac cannot be overridden. I followed this method, cleared web cache by using the personality menu from the task pane, and remove everything in ~/Library/Containers/com.microsoft.Excel/Data/Library/Caches/. But the old version was still there and could not be overridden by the new version from the Store.
Does anyone know what's happening here?
Did you try first removing the old version?
How to uninstall an Add-in (Mac)
If you wish to uninstall an Add-in completely, delete, move or rename the original Add-in file.
When ticking or unticking the Add-in, a message box will appear, asking for permission to delete the reference to the Add-in. Click Yes.
The Add-in will no longer appear in the list of Add-ins.
(Source)
Related
We deployed Excel add-in project which was developed in Office Js in intranet. And manifest file uploaded in Office 365 admin center to reflect users. But it is working in Office online Excel version only. But in desktop version it is not getting refreshing and only showing old changes. Kindly help on this so that it can be upload with new changes to get reflect.
You can remove an add-in that you've previously sideloaded on Windows, Mac, or iOS by clearing the Office cache on your computer.
Additionally, if you make changes to your add-in's manifest (for example, update file names of icons or text of add-in commands), you should clear the Office cache and then re-sideload the add-in using updated manifest. Doing so will allow Office to render the add-in as it's described by the updated manifest.
To remove all sideloaded add-ins from Excel, Word, and PowerPoint, delete the contents of the folder:
%LOCALAPPDATA%\Microsoft\Office\16.0\Wef\
To remove a sideloaded add-in from Outlook, use the steps outlined in Sideload Outlook add-ins for testing to find the add-in in the Custom add-ins section of the dialog box that lists your installed add-ins. Choose the ellipsis (...) for the add-in and then choose Remove to remove that specific add-in. If this add-in removal doesn't work, then delete the contents of the Wef folder as noted previously for Excel, Word, and PowerPoint.
Additionally, to clear the Office cache on Windows 10 when the add-in is running in Microsoft Edge, you can use the Microsoft Edge DevTools.
Read more about that in the Clear the Office cache article.
Do you know if this is possible to create a VSTO add-in for excel in an office 365 suite (on desktop, of course)?
Officially, it says it is supported.
But, if I create an empty project on VisualStudio with the default "Office 2013 & 2016 VSTO add-in", it does not load.
But, it works on other machines, with excel 2016.
Can you help me with this?
I already tried many things. And, it seems that the add-in does not even show in the list of COM add-ins in the setup menu. It's not disabled; and, if I look at the registry, the load behavior is 3.
The only strange thing that I found is that when I try to link manually the .dll file using the "add-in" menu, it says that the dll is not a valid excel add-in.
But, if I do it another way and click to the .vsto file, the explorer says that the add-in has been installed correctly..
Thanks a lot
I have an application that is developed using CommanBar tools. As there are much constraints in that, i have planned to shift to the Ribbon(view designer). I created a project like, File->New Project->Excel 2007->Excel Addin for 2010.
Created a sample addin and added a new project to the same solution as I wanted the addin to be added using installer(.msi). I registered the Com Addin in the Registry, but on uninstallation, the files are getting removed only in the registry entry, but not in the MS Excel, the addin still to be remained there. Please help me in this. As I am new to the implementation of Ribbon implementation.
I have used winform c# 4.0.
Thanks in advance.
#kiru - the screen shot for the path you mentioned
Check the path from where the addins are been loaded.
Open Excel
Click File => Options => Addins (Tab)
Select COM Add-ins in Manage dropdown box and click Go
Select the addin and you can see the path where it is been loaded.
If it is from bin directory then follow this
If you are running your msi on development pc clean your solution every time you test your msi.
Using Excel 2010 and TFS 2010. I've been using the "Team" tab in Excel for quite a while now (very useful!). Today, the "Refresh" took ages and I couldn't use Excel so I killed the process in Task Manager. I reopened Excel and the Team tab was missing. I added it back in File > Options > Add Ins > Manage COM Add Ins > Go > selected the Team Foundation Add-In and the Team tab is back. I can create/view lists etc. However, when I close and reopen Excel the Team tab is missing again.
How do I make the Team tab stay on the ribbon bar even when closing & reopening Excel?
For Excel 2013 x64 and Visual Studio 2012, I had to change HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\TFCOfficeShim.Connect.4\LoadBehavior to 3 (Load at startup).
I had previously disabled the add-in via the Excel COM Add-Ins dialog box. This changed the add-in load behavior to "do not load automatically". Attempting to re-enable the add-in through the dialog box now only changes it to "load on demand", which is only good for one session of Excel. There is an issue logged in Connect for this. Changing the registry manually works around the bug.
By chance, I re-enabled it (after having to manually re-add the tab again).
Excel > File > Options > Add-Ins > Manage > Disabled Items > select items > click Enable.
As easy as that.
I have had that same issue with TFS 2010 Office Add-in and Excel. The reason was because there were two TFS Office add-ins, the first version was for a 64 bit machine, while the other was for a 32 bit machine. So I removed both versions, restarted excel, and re-added the 32 bit version of the TFS add-in. I have had no issues since.
EDIT: My local machine is running Windows 7 64 bit and Excel 2010.
I just ran into this myself. The registry setting looked okay, and there weren't any add-ins listed under Disabled Items.
I launched Excel as Administrator, deleted all instances of Team Foundation Add-in (I had 3), and then re-added the add-in. It was then correctly showing as "Load at Startup." I closed Excel and re-opened from my usual shortcut, and everything looked good.
There were a number of Excel restarts peppered into that process as I was very much guessing and checking, but I believe that it was the act of re-adding the add-in that ultimately resolved the issue for me.
I had to remove the extension (listed as "Unloaded") from COM Add-Ins list and then add it again.
Follow the instructions below to manually add it to Excel:
Navigate to Com Add-ins manager:
File > Options > Add-Ins > set "Manage:" to "COM Add-ins" > Go...
Add it again:
Add... > "C:\Program Files\Common Files\Microsoft Shared\Team Foundation Server\11.0\x86\TFSOfficeAdd-in.dll" > OK
Restart Excel: Confirm the "Team" tab appears on startup
This is a workaround that helps several people. This is not a fix but still has worth.
Launch Excel as Administrator. You do this by right clicking the Excel Icon, then right click the Excel mini-icon then click "Run as administrator".
This is not a fix and can be a hassle but for many with this issue it will provide the features you want. Hopefully Microsoft will come up with a permanent solution in the future.
With latest versions this problem can be solved by installing Azure DevOps Office® Integration 2019 from
https://visualstudio.microsoft.com/downloads/#other-family
If you don't see Team Foundation Add in you can use this method which saved a lot of time for me
it will appear like this , file --> options --> add ins
I have a VSTO Excel workbook project that I can debug fine on my laptop. The project solution also accesses some special hardware on another computer and the project was debugging there fine yesterday in VS2010. Today, it stopped hooking into Excel on debugging on this computer. F5 starts Excel, but the add-in doesn't load breakpoints in the Workbook startup events, etc... Same project from version control debugs fine on my laptop, so something is whacked with Excel or VS on this computer. I’ve seem some related notes/posts on VSTO logging and resetting Excel, but has any beat their head against this?
UPDATE: this solution didn't work for me.
As I was typing I found this similar and promising title...
Excel won't open/launch VSTO AddIn when running in debug mode of Visual Studio 2010
My issue occurred due to having the release version of the app installed and trying to run the debug version. Have to then uninstall the release version, Clean then Build, then re run the add in.
Weird!
Just check if the add-in is disabled.
Office menu > {Word/Excel/PowerPoint} Options > Under “Manage” select “Disabled Items” and then click Go.
For more information read http://blogs.msdn.com/b/vsod/archive/2008/04/22/troubleshooting-com-add-in-load-failures.aspx
/Artha Wijendra
You may need to completely wipe all traces of previously installed versions of your VSTO. Try this:
Remove the registry key for your VSTO from HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Excel\AddIns. If you're working with Office 32-bit on a 64-bit machine then look in HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Microsoft\Office\Excel\AddIns.
Remove folder C:\Users\ {username} \AppData\Local\Apps\2.0 (You may need to reboot the machine first to release locks on files within this folder structure.)
Open Excel. Go to Files > Options > Add-Ins > Manage COM Add-Ins and remove your VSTO if it is listed.
Clear the ClickOnce cache by typing this at the command prompt: rundll32 dfshim CleanOnlineAppCache
If that still doesn't work then also try removing all keys/values from the registry that reference your VSTO and its related assemblies.
When my Excel Add-In would not load when I hit "Start" in Visual Studio to debug, all I ended up doing to fix the issue was "Rebuild" my solution.