5 ms·

I work on Excel and this is really cool and I’ll share it with the rest of the engineers.

• inglor 4y ago
  Team says it’s cool and already possible with different us through https://learn.microsoft.com/en-us/office/client-developer/excel/developing-excel-xlls https://learn.microsoft.com/en-us/office/client-developer/ex... https://learn.microsoft.com/en-us/office/troubleshoot/excel/set-up-realtimedata-function https://learn.microsoft.com/en-us/office/troubleshoot/excel/...
  • ripley12 4y ago
    I mean... sorta. It's not easy to write a Office add-in just using the C API, and when I tried a year or two ago the only example code I could find was like 20 years old and all documentation was heavily pushing people toward the newer JS-based add-ins. I quit that job because the extensibility story for Excel was so painful (but they had good business reasons for being in the space), sigh.
  • airstrike 4y ago
    Writing an XLL add-in is a terrible pain I wish on no one at all. The documentation is all over the place, terribly outdated and generally an aggravating process to try to learn it from scratch
  • sharpcells 4y ago
    We use those APIs internally to implement Sharp Cells. You can certainly build your own integration however the XLL API in particular was poorly documented and very difficult to implement correctly. Sharp Cells' aim is to make it easy to use these APIs from F# so you don't have to worry about P/Invoke, manual memory management, dynamic .NET assembly loading, etc. to just write custom functions.