Daniel, your software is amazing.
Unfortunately, after noticing on Windows 10 in the Office 365 version of Excel that the XL Toolbox tab was gone (it previously worked fine for months), I uninstalled then reinstalled.
The installation process went fine as admin.
But when I try to add the XL Toolbox from the Excel>DeveloperTab>Add-ins>COM Add-Ins, the check option showed that the tool was unloaded.
Picture:
I had tried numerous times to check the box and press OKā¦ nothing changed.
I also checked the registry, and everything seemed to be in its right place.
My only thought was that the Location: āfile:///C:/Users/ā¦ā might be causing an issue. I only noticed because the other addins were all in the program files directories.
So, I unsinstalled. Then I reinstalled (XLToolbox-7.3.4.exe) as admin and used āC:\Program Files\XLToolboxā as the directory. Everything is now working as expected.
I began writing this post while it was not loaded, then solved the problem. So, this is a potential bug report, but I donāt really need followup.
Between the last time I used the XLToolbox and today, there was a server migration. So, maybe that had something to do with it. I have no idea.
Thanks for this report! Over the past months, I have received a number of similar reports. While I personally have not experienced problems installing the Toolbox on Office 365/Windows 10, others users do. Itās unpredictable. Your solution might help others get it installed after all.
Microsoft have introduced a new āapplication programming interfaceā (API) for Office add-ins, which is based on JavaScript. While they still support the traditional .NET-based add-ins (with something called āVisual Studio Tools for Officeā, VSTO), and even still support the ancient Visual Basic for Applications, I get the impression that JavaScript is the future of Office add-in development.
While I would love to explore moving the XL Toolbox to JavaScript, this would be yet another major rewrite of this add-in (which used to be a plain old Visual Basic for Applications add-in). At the same time, I have close to zero spare time to even maintain this add-in. So Iām glad when users find a way to make it work for themselves.
An additional issue is that I really should code-sign the add-in, i.e. use a cryptographic certificate to prove the authenticity of the add-in. Unfortunately, these certificates cost a lot of money and have to be renewed on an annual (or biennial, ā¦) basis. If I were to do this, Iād have to change the business model and offer the add-in for money. I donāt really want to to that. However, code-signing would probably solve a lot of installation issues, because Microsoft get more and more picky (and rightly so) about installing pieces of software that are not signed with a certificate.
we have a similiar problem with the not signed add-in so we cant get it working because only signed add-ins are allowed. For free code signing certificates you can go to http://www.cacert.org/
cacert is not listed as a Microsoft Trusted Root Program Participant (ref. 1, ref. 2), just like their CA is not included in the major internet browsers. I appreciate your comment, but Iām afraid the code signature would not be accepted.
but the browsers are not involved into this topicā¦ It doesnt matter if any browser would trust your certificate but i would give me (or any other admin) the possibility to add this Cacert certificate to the ātrusted publisherā store so it can run even if only signed add-ins are allowed.
sorry for the late reply, I was really busy lately. Youāre right, browsers are not involved ā that was just meant to be an example of another use case. It is my understanding however that the āMicrosoft Trusted Root Programā refers to the operating system itself. Anyway, I did look into purchasing a āproperā (widely trusted) certificate. This requires me to have my identity verified by a notary public, and thatās were Iām currently stuckā¦
