Building Office Add-ins using Office.js
$15.99
Minimum price
$19.99
Suggested price

Building Office Add-ins using Office.js

About the Book

This book is about creating Office Add-ins – and in particular, about the Office 2016+ wave of Office.js APIs.

Want to get started with just the very core concepts, before buying the book? Download some sample chapters, or better yet, buy the book regardless: I am sure you'll find the topics therein new and useful for writing add-ins; and if you don't, LeanPub's Happiness Guarantee will let you get a full refund anytime in the first 45 days.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

All proceeds from this book will be donated to humanitarian work / disaster relief (and also get matched by Microsoft's generous Employee Match program, for double impact). See the detailed accounting here.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Office 2016 has seen a major re-birth of the API model, with hundreds of new APIs created for Excel and Word and OneNote. These APIs are cross-platform, are built on a modern web framework, and offer some of the same powerful functionality that previously was only available on the Desktop.

In spirit, the new Office.js APIs are reasonably similar to their VBA/VSTO counterparts, but with the notable difference of being async  which brings with it a new set of concepts and best practices. This book will begin by address the core concepts to help you get over the initial learning curve, and get started on using the APIs. The subsequent chapters will expand upon these topics, covering more advanced scenarios, and offering debugging advice, tips, FAQs, and so forth.

Yours truly,

- Michael Zlatkovsky, the author (and member of the Office API team from 2015-2019)

About the Author

Michael Zlatkovsky
Michael Zlatkovsky

This book is written for Office Developers, by an Office Developer. By the latter, I mean both that I had been a developer who used Office technology extensively for a number of years, and that I am now a developer on the Office Extensibility Platform team – the very team that created Office Add-ins.

Having been a key participant in the design of the new Office 2016 wave of Office.js APIs – and having seen folks embrace the framework, but struggle with some of the more concepts – I wanted to share some insights & techniques, as well as the full end-to-end story, of how to create Office Add-ins.

You can find me on StackOverflow, where I frequently answer questions tagged as "[office-js]" (which has been a source of inspiration for many sections of this book).  I have a backlog of topics I want to cover in this book: some already fleshed out, others less so.  In the spirit of the "lean" methodology, I will be updating the book frequently as I cover more and more topics.  Thanks for reading, and please feel free to contact me for feedback on the book, requests for topics, etc.

Yours truly,

- Michael Zlatkovsky

Packages

The Book
  • PDF

  • EPUB

  • WEB

  • English

$15.99
Minimum price
$19.99
Suggested price
3 Copy Package

This package is for THREE copies of the book, to distribute among your Dev team, at a small discount. After checkout, in the confirmation/download page, you will see "You have purchased multiple copies of this Book. Click here to manage your download tokens." You can use this to send out the individual tokens to team members. That way, only one person (e.g., a team admin with a corporate credit card) needs to go through the checkout process, and the rest can just download the book.

  • PDF

  • EPUB

  • WEB

  • English

$45.00
Minimum price
$55.00
Suggested price
5 Copy Package

This package is for FIVE copies of the book, to distribute among your Dev team. After checkout, in the confirmation/download page, you will see "You have purchased multiple copies of this Book. Click here to manage your download tokens." You can use this to send out the individual tokens to team members. That way, only one person (e.g., a team admin with a corporate credit card) needs to go through the checkout process, and the rest can just download the book.

  • PDF

  • EPUB

  • WEB

  • English

$75.00
Minimum price
$85.00
Suggested price

Table of Contents

  • 1 The book and its structure
    • 1.1 The “evergreen”, in-progress book
    • 1.2 Release notes
    • 1.3 Bug reports / topic suggestions
    • 1.4 Twitter
    • 1.5 Who should read this book
    • 1.6 From the author
    • 1.7 A few brief notes
    • 1.8 Acknowledgments
  • 2 Introduction to Office Add-ins
    • 2.1 What’s “new” in the Office 2016 APIs (relative to 2013)?
    • 2.2 What about VBA, VSTO, and COM Add-ins?
    • 2.3 “But can Office.js do XYZ?”
    • 2.4 A word on JavaScript and TypeScript
    • 2.5 Office.js: The asynchronous / deferred-execution programming model
      • 2.5.1 Why is Office.js async?
      • 2.5.2 What is meant by “the server”
  • 3 Getting started: Prerequisites & resources
    • 3.1 Script Lab: an indispensable tool
    • 3.2 The optimal dev environment
    • 3.3 API documentation resources
  • 4 JavaScript & Promises primer (as pertaining to our APIs)
    • 4.1 “JavaScript Garden”, an excellent JS resource
    • 4.2 JavaScript & TypeScript crash-course (Office.js-tailored)
      • 4.2.1 Variables
      • 4.2.2 Variables & TypeScript
      • 4.2.3 Strings
      • 4.2.4 Assignments, comparisons, and logical operators
      • 4.2.5 if, for, while
      • 4.2.6 Arrays
      • 4.2.7 Complex objects & JSON
      • 4.2.8 Functions
      • 4.2.9 Functions & TypeScript
      • 4.2.10 Scope, closure, and avoiding polluting the global namespace
      • 4.2.11 Misc.
      • 4.2.12 jQuery
    • 4.3 Promises Primer
      • 4.3.1 Chaining Promises, the right way
      • 4.3.2 Creating a new Promise
      • 4.3.3 Promises, try/catch, and async/await
  • 5 Office.js APIs: Core concepts
    • 5.1 Canonical code sample: reading data and performing actions on the document
    • 5.2 Excel.run (Word.run, etc.)
    • 5.3 Proxy objects: the building-blocks of the Office 2016 API model
      • 5.3.1 Setting document properties using proxy objects
      • 5.3.2 The processing on the JavaScript side
      • 5.3.3 The processing on the host application’s side
      • 5.3.4 Loading properties: the bare basics
      • 5.3.5 De-mystifying context.sync()
    • 5.4 Handling errors
      • 5.4.1 The basics of Office.js errors
      • 5.4.2 Don’t forget the user!
      • 5.4.3 Some practical advice
    • 5.5 Recap: the four basic principles of Office.js
  • 6 Implementation details, if you want to know how it really works
    • 6.1 The Request Context queue
    • 6.2 The host application’s response
    • 6.3 Back on the proxy object’s territory
    • 6.4 A special (but common) case: objects without IDs
  • 7 More core load concepts
    • 7.1 Scalar vs. navigation properties – and their impact on load
    • 7.2 Loading and re-loading
    • 7.3 Loading collections
    • 7.4 Understanding the PropertyNotLoaded error
      • 7.4.1 What does it even mean?
      • 7.4.2 Signaling your intentions: an analogy
      • 7.4.3 Common mistake: re-invoking get methods (and in general, loading on methods versus properties)
      • 7.4.4 Another common mistake: loading nonexistent properties
      • 7.4.5 A rarer and more befuddling case: when using an object across run-s
    • 7.5 Methods that return “primitive” types (strings, numbers, etc). E.g.: tables.getCount(), chart.getImage(), etc.
  • 8 More core sync concepts
    • 8.1 Real-world example of multiple sync-calls
    • 8.2 When to sync
    • 8.3 The final context.sync (in a multi-sync scenario)
    • 8.4 A more complex context.sync example:
    • 8.5 Avoiding leaving the document in a “dirty” state
  • 9 Checking if an object exists
    • 9.1 Checking via exception-handling – a somewhat heavy-handed approach
    • 9.2 A gentler check: the *OrNullObject methods & properties
      • 9.2.1 Case 1: Performing an action, and no-op-ing otherwise
      • 9.2.2 Case 2: Checking whether the object exists, and changing behavior accordingly
  • 10 Excel.run (Word.run, etc.) advanced topics
    • 10.1 What does “.run” do, and why do I need it?
    • 10.2 Using objects outside the “linear” Excel.run or Word.run flow (e.g., in a button-click callback, in a setInterval, etc.)
      • 10.2.1 Re-hydrating an existing Request Context: the overall pattern, proper error-handling, object.track, and cleanup of tracked objects.
      • 10.2.2 A common, and infuriatingly silent, mistake: queueing up actions on the wrong request context
      • 10.2.3 Resuming with multiple objects
      • 10.2.4 Why can’t we have a single global request context, and be one happy family?
  • 11 Other API Topics
  • 12 The practical aspects of building an Add-in
    • 12.1 Walkthrough: Building an Add-in using Visual Studio
    • 12.2 Getting started with building TypeScript-based Add-ins
      • 12.2.1 Using Visual Studio
      • 12.2.2 Using Yeoman generator & Node/NPM
    • 12.3 Debugging: the bare basics
    • 12.4 IntelliSense
    • 12.5 Office versions: Office 2016 vs. Office 365 (MSI vs. Click-to-Run); Deferred vs. Current channels; Insider tracks
    • 12.6 Office.js API versioning
      • 12.6.1 The JavaScript files
      • 12.6.2 The host capabilities
      • 12.6.3 The Beta Endpoint
      • 12.6.4 How can you know than an API is “production-ready”?
  • 13 Appendix A: Using plain ES5 JavaScript (no async/await)
    • 13.1 Passing in functions to Promise .then-functions
    • 13.2 JavaScript-only version of the canonical code sample
    • 13.3 JavaScript-specific sync concepts
      • 13.3.1 A JavaScript-based multi-sync template
      • 13.3.2 Returning the context.sync() promise
      • 13.3.3 Passing values across .then-functions
      • 13.3.4 JavaScript example of multi-sync calls
  • 14 Appendix B: Miscellanea
    • 14.1 Script Lab: the story behind the project
  • Notes

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

So, there's no reason not to click the Add to Cart button, is there?

See full terms...

Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earnedover $14 millionwriting, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub