You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
.xll got auto opened as shown in attached photo.
The text was updated successfully, but these errors were encountered:
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.
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.
.xll got auto opened as shown in attached photo.
The text was updated successfully, but these errors were encountered: