Name: Outlook-Add-in-JavaScript-ModuleExtension
Owner: Office Developer
Description: null
Created: 2016-03-23 22:48:52.0
Updated: 2018-05-04 15:27:17.0
Pushed: 2017-12-28 21:34:50.0
Homepage: null
Size: 179
Language: JavaScript
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
This Outlook 2016 for Windows add-in sample uses the new module extenstion point
March 31, 2016:
April 4, 2016:
You'll need to install a certificate to run this sample because add-in commands require HTTPS. Because add-in commands to not have a UI, you are not prompted to accept an invalid certificate.
`./gen-cert.sh
` to create a certificate.`ca.crt
` and install it in your Trusted Root Certification Authorities storeStart a local HTTPS web server to serve the files for the module extension:
`npm install
` in the project root directory`node server.js
`It may take Outlook a few moments to load the new module, but when it does you'll see your new module added to the navigation bar shortcuts. Using compact navigation, the shortcuts look like this:
If you're not using compact navigation, the shortcuts will look like this:
Click either Billable hours or the module icon to open the module extension. Outlook will change to show the module UI.
There are three buttons on the ribbon. Click one to change the billing rate, and the totals in the main UI will change to reflect the new rate.
The new module extension is enabled in your manifest file by setting the extension type to `"Module"
`. This is the section of the manifest that you need to change:
<!--New Extension Point - Module for a ModuleApp -->
<ExtensionPoint xsi:type="Module">
We'd love to get your feedback on the Outlook-Add-in-JavaScript-ModuleExtension sample. You can send your feedback to us in the Issues section of this repository.
Questions about Office 365 development in general should be posted to Stack Overflow. Make sure that your questions are tagged with [Office365] and [API].
Copyright (c) 2016 Microsoft. All rights reserved.
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.