Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xll got auto-opened in Excel UI #108

Open
4R3B3LatH34R7 opened this issue Jan 1, 2022 · 3 comments
Open

xll got auto-opened in Excel UI #108

4R3B3LatH34R7 opened this issue Jan 1, 2022 · 3 comments

Comments

@4R3B3LatH34R7
Copy link

4R3B3LatH34R7 commented Jan 1, 2022

Office365 Excel 64bit with Excel-DNA Intellisense 1.4.2.xll, Win10 64bit.
Unblocked already in C: users addins directory.
When .xlsm was opened, xll was auto-opened as readonly in UI as well, with every xlsx and xlsm.
Cannot uncheck the addin from Developer - Addins menu.
Had to manually delete the .xll.
Error message as shown in attached photo.
excel-dna intellisense error message
.xll got auto opened as shown in attached photo.
excel-dna intellisense auto opened

@govert
Copy link
Member

govert commented Jan 1, 2022

That error message normally means that you are opening the 64-bit version of the add-in in a 32-bit installation of Excel (or vice versa).

@govert
Copy link
Member

govert commented Jan 1, 2022

Maybe you can show a screenshot of the Excel version (File -> Account -> About Excel). I have this:
image

@4R3B3LatH34R7
Copy link
Author

Yes, you are right, my user was quite adamant that her Office365 was 64bit.
Problem was solved by using 32bit xll.

The only issue left was: if .xlsm(containing Intellisense worksheet) was double clicked to open, the Intellisense doesn't work for UDF and needs to close the file from File menu then open .xlsm again to get Intellisense working.
However, if Excel were run first, then open .xlsm from recent list, Intellisense kicked in immediately.
Excel-DNA Intellisense host was checked in Developer-Addins in both scenarios.
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants