For https://github.com/Hongbo-Miao/office-addin-react

First npm i, then follow the steps below:

You will reproduce the issue.

Sample files
manifest-sample-fail.xml.txt
manifest-sample-pass.xml.txt

Using version 0.3.0, this node structure results in a failure:

<VersionOverrides ...>
  <EquivalentAddins>
  </EquivalentAddins>
  <Hosts>
  </Hosts>
  <Resources>
  </Resources>
</VersionOverrides>

Validate output:

Validation: Failed

Error #1:
XML Schema Violation: Your manifest does not adhere to the current set of XML schema definitions for Office Add-in manifests. (link: https://aka.ms/add-in-manifest-schema-violation)

• Details: The element 'VersionOverrides' in namespace 'http://schemas.microsoft.com/office/taskpaneappversionoverrides' has invalid child element 'Hosts' in namespace 'http://schemas.microsoft.com/office/taskpaneappversionoverrides'. List of possible elements expected: 'ConnectedServiceControls' in namespace 'http://schemas.microsoft.com/office/taskpaneappversionoverrides' as well as any element in namespace 'http://schemas.microsoft.com/office/taskpaneappversionoverrides/1.1'.

Yet this succeeds:

<VersionOverrides ...>
  <Hosts>
  </Hosts>
  <Resources>
  </Resources>
  <EquivalentAddins>
  </EquivalentAddins>
</VersionOverrides>

If a certain ordering is required for VersionOverrides child elements, it would be helpful to specify that in the VersionOverrides documentation.

It would be nice to open a specific file.
We would pass the file path after the flag "--file" or "-f".

Usage suggestions:
office-toolbox sideload -m my/add-in/manifest.xml -a word --file /path/to/file.docx
OR
office-toolbox sideload -m my/add-in/manifest.xml -a word -f /path/to/file.docx
-f /path/to/file.docx

And it would sideload the add-in in the specified file.

I cannot get my sideloaded TaskPane Excel add-in to reflect changes in the manifest.xml. I've changed all https locations to dummy strings that should fail, but when I sideload the add-in, Excel is pulling from the old manifest.xml somehow.

Short of uninstalling and reinstalling Excel, I've tried everything I can think of.

• Running sideload from a different location
• Doing a search of all files in my filesystem with the name "manifest.xml" and deleting those.
• Deleting every cached item from /User/AppData/Local/Microsoft/Office/16.0/Wef/
• Deleting everything from /User/AppData/Roaming/Microsoft/Windows/Recent Items

How can I update my manifest?

... Though if we do directory-based browsing, that become potentially irrelevant:

Whenever an Outlook add-in manifest contains duplicate resource IDs, the add-in installs successfully, however, it doesn't show up in the native Windows Outlook and Mac Outlook clients. It, however, shows up in the online Outlook client (Outlook Web Access / OWA).

It will be very helpful if the Office add-in manifest validator could detect duplicate resource IDs.

This request is a result of an actual issue reported by a customer where an add-in which had been successfully validated by the validation tool failed to show up in the native Outlook client.

The sideload option allows our less technical QA to use development builds of our addin. To simplify using the addin on specific documents, it would be great if the file that get loaded could get configured.

What about also allowing an argument instead of calling generateTemplateFile in sideloadManifest?

"office-toolbox sideload -validate" would run validation

Github issue - OfficeDev/office-js#1074

RequestedHeight tag should come after label tag and before SourceLocation tag must appear in the manifest validation tool

(Strangely, seems to have quite itself after ~20 seconds; but perhaps that was just me pressing something)

Not sure I'm in love with dumping the file at the root; see the effect it had on source control, for example, for a file that I have no intention to check in. And it's not necessarily a name I would have chosen.

I would recommend dumping to a temp directory instead. If someone wants to keep the file, they can always "save as" it.

Summary: I am trying to sideload an manifest file named manifest.xml on macOS when my /wef/ directory already has a manifest.xml from another addin. office-toolbox notices that they are two different files (because they have different dev/inodes) and refuses to sideload my manifest file.

Expected behaviour: office-toolbox should alert the user that the manifest file was not sideloaded.

Actual behaviour: office-toolbox acts as if the manifest file was sideloaded.

Relevant source code:

Suggested change: I believe that the two manifest files are different if stat.dev and stat.ino are different. This lines checks BOTH are different. This should be changed.

Ran: npm install -g office-toolbox

c:\dev>npm install -g office-toolbox
npm WARN deprecated [email protected]: ...psst! Your project can stop working at any moment because its dependencies can change. Prevent this by migrating to Yarn: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

I added a requirement set of ExcelAPI 1.9 to my manifest file. Based on https://docs.microsoft.com/en-us/office/dev/add-ins/overview/office-add-in-availability, this version is only supported on 'Office on the web', 'Office on Windows (connected to Office 365 subscription)' and 'Office on Mac (connected to Office 365 subscription)'.

But when I validate my manifest file. The output I received is this:

Validation: Passed
Based on the requirements specified in your manifest, your add-in can run on the following platforms; your add-in will be tested on these platforms when you submit it to the Office Store:
  - Excel 2016 for Mac
  - Excel 2016 or later
  - Excel Online
Important: This analysis is based on the requirements specified in your manifest and does not account for any runtime JavaScript calls within your add-in. For information about which API sets and features are supported on each platform, see Office Add-in host and platform availability. (https://dev.office.com/add-in-availability).

With Excel API 1.9, do you think it will still work in Excel 2016 and 2019 standalone purchases?

I tried out office-toobox0.2.0 and "npx office-toolbox remove -a excel" will show the manifests, but if you pick one, it won't remove it.

Starting around March 18, 2019 we get:

C:\Sandbox\EY\FPP-OfficeAddins2\FPP-Excel-AddIn>npm run sideload

> [email protected] sideload C:\Sandbox\EY\FPP-OfficeAddins2\FPP-Excel-AddIn
> office-toolbox sideload -m manifest.xml -a Excel

ApplicationInsights:CorrelationIdManager [ { Error: unable to verify the first certificate
      at TLSSocket.onConnectSecure (_tls_wrap.js:1051:34)
      at TLSSocket.emit (events.js:189:13)
      at TLSSocket._finishInit (_tls_wrap.js:633:8) code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' } ]
ApplicationInsights:Sender [ 'Ingestion endpoint could not be reached. This batch of telemetry items has been lost. Use Disk Retry Caching to enable resending of failed telemetry. Error:',
  { Error: unable to verify the first certificate
      at TLSSocket.onConnectSecure (_tls_wrap.js:1051:34)
      at TLSSocket.emit (events.js:189:13)
      at TLSSocket._finishInit (_tls_wrap.js:633:8) code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' } ]
Deleted file: C:\Users\lewis\AppData\Local\Temp\excel add-in 841a65bf-dc23-4a21-8b2b-027515cc18e3.xlsx
Generating file C:\Users\lewis\AppData\Local\Temp\excel add-in 841a65bf-dc23-4a21-8b2b-027515cc18e3.xlsx
Opening file C:\Users\lewis\AppData\Local\Temp\excel add-in 841a65bf-dc23-4a21-8b2b-027515cc18e3.xlsx
For more information about how to sideload Office Add-ins, visit the following link: https://docs.microsoft.com/en-us/office/dev/add-ins/testing/create-a-network-shared-folder-catalog-for-task-pane-and-content-add-ins

The run-sideload function still owrks, but this message says there was an erorr

When Word is installed via the app store the sideload command throws the following exception:

The path where Word gets installed as app is:

C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Word_16051.11901.20120.0_x86__8wekyb3d8bbwe\Office16

I prefer to do most of my dev work / terminal interactions through WSL. This has worked out fairly well by mounting the c drive so that I can run visual applications like VS Code, but use an ubuntu terminal for things like actual yarn build. I would strongly prefer to not maintain a two dev environments (in and out of WSL).

I've tried using the sideload command in a plugin dev workflow, but the root path for the sideload directory is determined through os.home() which isn't quite the desired folder when operating through WSL, and can't be symlinked from my working directory:
Error: EXDEV: cross-device link not permitted, link '/mnt/c/Users/rniem/<dev path>/excel-plugin/my-office-add-in-manifest.xml' -> '/home/ricky/Library/Containers/com.microsoft.Excel/Data/Documents/wef/my-office-add-in-manifest.xml'

Ideally this would be configurable so that WSL support can work with the mounted directory.