Office 365 Registry Keys
Alan Stubbs
Govert van Drimmelen
--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To post to this group, send email to exce...@googlegroups.com.
Visit this group at https://groups.google.com/group/exceldna.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/e4e65793-f492-4d06-87fe-8b7c26ba4169%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gareth Hayter
On Thursday, 4 July 2019 05:27:11 UTC+12, Govert van Drimmelen wrote:
Maybe that Excel is running in an App-V / Click-to-run container or similar, confusing the registry view from outside Excel completely.I don't know much about the details but this might be a start: https://blogs.msdn.microsoft.com/vsod/2016/12/09/consdierations-while-readingwriting-registry-keys-under-hklm-from-office-addin-in-office-click-to-run/#comment-5815-Govert
On Wed, 3 Jul 2019, 19:08 'Alan Stubbs' via Excel-DNA, <exce...@googlegroups.com> wrote:
Hi Govert,--Hope you are well.I've got a curious client bug whereby the usual Registry entries under HKCU are completely missing, apparently - so various installation stages fail. He is running Office 365 MSO (16.0.11727.20222) 32-bit on Windows 10 64-bit - in Italian for what it's worth.There are various references to Office and Excel throughout Registry but not the usual .../Microsoft/Office key where I would set OPEN, etc.It seems to be a recent issue with 32-bit installs of Office 365 (other similar-sounding cases have been reported.) This case seems not to have been a Microsoft App Store install.The addin xll can be "installed" manually via Excel and works fine then.Have you seen this elsewhere? Is the relevant key in a different "Current User" somehow?Thanks,Alan
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exce...@googlegroups.com.
Alan Stubbs
Craig Crevola
HI Alan
I would agree with Gareth as I have had a similar problem with developing on a machine (Dell) at a client site where Office was preinstalled by Dell (runs as windows app store install). Visual Studio could not launch Excel for debugging (Excel DNA) because the expected paths to Excel did not exist. Curiously this did not effect VSTO. However, attaching a debugger to the installed Excel DNA addin worked just fine as did loading the addin manually (as you have observed). Here is a link for the new packaging format for Windows store apps: https://docs.microsoft.com/en-us/windows/msix/overview
If you search the registry for WindowsApps in values, you will find the registry settings for the Windows store Apps, as this is the folder they are deployed in the latest Win10 environments. You should see a key like this: Computer\HKEY_CLASSES_ROOT\AppXaf0097ws4bwb0wre67gmp7pc9fjr8en6 (this is from my OneNote installation). From there you can dig around using the Appxxxxx value as that is the activatable class id. If you have a look under : Computer\HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\PackageRepository\Packages\
You can see what has been installed as an app store package. That will give you the names which you can search further with.
Thanks
Craig.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To post to this group, send email to exce...@googlegroups.com.
Visit this group at https://groups.google.com/group/exceldna.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/545f6afd-57a0-496c-ada8-773ff269e008%40googlegroups.com.
