And I'm not talking about the plugin development hell (never had to work with it, but that seemed, erm, "difficult"). Feel free to reach out to me if you have questions, or just read the docs yourself (http://dev.office.com/).
And I'm not talking about the plugin development hell (never had to work with it, but that seemed, erm, "difficult"). Feel free to reach out to me if you have questions, or just read the docs yourself (http://dev.office.com/).
The office team moving away from the old plugin model and opening up the gates for JS apps and REST APIs made life dramatically easier for a lot of folks. So I assume that samples were written with the most popular choices in mind. Internally, C++ is king [0], of course.
It's also worth pointing out that we always accept code samples from the community :)
[0]: https://code.msdn.microsoft.com/office/site/search?f%5B0%5D.... [1]: http://cppcon.org/bonus-talk-cxx-in-ms-office-2014/