I've created an SSO-enabled Outlook add-in by using the Yeoman generator and running npm run configure-sso (as described in the SSO quick start). I'm unable to successfully run this add-in in Outlook on the web, due to error $ is not defined being thrown from message-helper.js in the Office Add-in SSO package.

Screenshot:

Currently, --dev-server <command> specifies to run the packager and --dev-server-port <number> specifies to check whether the dev-server is running on the port.

Consider simplifying into a single --dev-server <url> [command] option. If present it would indicate to ensure that the dev-server is running (using the url or the port parsed from the url), and it would start the dev-server if not already running using the specified command.

For example: office-addin-debugging start manifest.xml --dev-server https://localhost:3000 "npm run dev-server"

Similarly, the --packager option could be updated to use --packager <url> [command].
For example: office-addin-debugging start manifest.xml --packager http://localhost:8081 "npm run packager"

Expected Behavior

According to the docs (https://docs.microsoft.com/en-us/office/dev/add-ins/reference/manifest/version), the manifest file requires the version to be structure with 4 numbers (<Version>n .n .n .n</Version>). Manifest validation should pass when the version follows (e.g. 1.0.0.0) and should fail when it does not (e.g. 1.0.0).

Current Behavior

Starting with a valid manifest file, change the version to something that only has 3 numbers in it (e.g. 1.0.0). Attempt to validate this manifest file again. Validation still passes. This is very problematic for debugging -- This version actually is accepted by Desktop Excel, but fails when trying to install the add-in with Excel in the browser. Both desktop and Excel Online should both handle the manifest in the same manner. Since this pertains specifically to the manifest being invalid, though, this could be headed off at the pass if the manifest validation simple would fail and let the user know that their version is not valid.

Steps to Reproduce, or Live Example

Follow the steps in this tutorial: https://docs.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-custom-functions-quickstart?tabs=excel-windows

After running yo office, select the following options:

? Choose a project type: Excel Custom Functions Add-in project
? Choose a script type: JavaScript
? What do you want to name your add-in? My Office Add-in

1. Run npm run validate. Works!
2. Build the add-in with npm run build and then run it with npm start.
3. Open the add-in in Excel Desktop. Works!
4. Open the add-in in Excel Online (by uploading the manifest.xml file). Works!

Now, edit the manifest.xml file and change the version from <Version>1.0.0.0</Version> to <Version>1.0.0</Version>. Run npm stop and then follow the exact same steps above.

1. Run npm run validate. Works! (even though it should error out because the version in invalid according to the manifest.xml docs (https://docs.microsoft.com/en-us/office/dev/add-ins/reference/manifest/version)
2. Build the add-in with npm run build and then run it with npm start.
3. Open the add-in in Excel Desktop. Works!
4. Open the add-in in Excel Online (by uploading the manifest.xml file). Fails. This is the error message that loads right away after uploading the manifest file:

Context

This issue actually me about a day's worth of work as I thought there was actually an issue with my custom function. Since the error message attached is shown before any code is called, there is no way to debug what is going on. If the error messages were a bit more clear and stated that there was an error in the manifest file (or even better -- WHAT is wrong in the manifest file), that would probably go a long way to making this a better experience.

Your Environment

• Platform [PC desktop, Mac, iOS, Office Online]: PC desktop & Office Online
• Host [Excel, Word, PowerPoint, etc.]: Excel
• Office version number:

  Microsoft Excel for Office 365 MSO (16.0.12022.20000) 64-bit
  Version 1902 (Build 12022.20000 Click-to Run)
  Office Insider

• Operating System: Windows 10
• Browser (if using Office Online):

  Google Chrome | 76.0.3809.100 (Official Build) (64-bit) (cohort: Stable)
  Revision: ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
  OS: Windows 10 OS Version 1903 (Build 18362.295)

Useful logs

• Console errors
• Screenshots
• Test file (if only happens on a particular file)

On macOS 10.14.5, starting the debugger with npm run start which runs office-addin-debugging start manifest.xml spins up a debugging server but in a detached process. Running npm run stop or office-addin-debugging stop manifest.xml does not stop the process.

The only way I was able to get it to stop was to find the node process that had port 3000 open and kill it with Activity Monitor.

On Mac, if the dev certs are not installed and the dev-server is not running, the office-addin-debugging start command will start the dev-server as a detached process. Since there is no window, the user cannot enter the password for the dev certs. After 30 seconds it times out.

The following will not generate metadata properly:

/**
  * @customfunction
  * A custom function
  */
function custom() {
}

It appears that it is related to the @customfunction tag which now takes optional id and name, and it reads the next line as part of the tag. So the "A" is read as the id and "custom" is read for the tag resulting in metadata:
{
"id": "A",
"name": "custom",
}

expected metadata:
{
"id": "CUSTOM",
"name": "CUSTOM",
}

• Use the TypeScript compiler JSDoc support to parse the @param type rather than just reading the string. Unify the code for parameter types from @param versus parameter types from TypeScript directly.
• The error messages need to be improved.
• The code needs to be refactored so that the metadata type/dimensionality is treated as a unit.
• Need better test coverage of simple parameter types, array types, invocation parameter types, other JavaScript/TypeScript types (enum, union, object, Error, etc.)
• There is lots of opportunity to make the code more modular and readable.

Hey all,

Thanks for putting a package together to assist in the validation of a manifest.

Not sure if this is an issue with my install or what but the office-addin-manifest package does not appear to work out of the box for me. Exact steps below.

Version check + install

C:\Users\SeanK> node -v
v10.16.3
C:\Users\SeanK> npm -v
6.9.0
C:\Users\SeanK> npm install -g office-addin-manifest
C:\Program Files\nodejs\office-addin-manifest -> C:\Program Files\nodejs\node_modules\office-addin-manifest\cli.js
+ [email protected]

So far so good. I re-open the window but then I can't get it to tell me what version it is:

C:\Users\SeanK> office-addin-manifest
Usage: office-addin-manifest [options] [command]

Options:
  -V, --version                     output the version number
  -h, --help                        output usage information

Commands:
  info <manifest-path>
  modify [options] <manifest-path>
  validate <manifest-path>
C:\Users\SeanK> office-addin-manifest -V
(version not available)
C:\Users\SeanK> office-addin-manifest -v
error: unknown option `-v'

And when I validate a manifest that I copied from the docs I can't get the tool to provide a response:

C:\Users\SeanK> office-addin-manifest validate C:\Users\SeanK\Repositories\[Redacted]\AppManifest.xml
Error: The manifest validation service did not return the expected response.

I pulled up Fiddler to see if any traffic was going out to a validation service but that doesn't appear to be the case.

Version info

To recap the above:

• Winver: Windows 10 Build 1903 (18362.356)
• Node: 10.16.3
• Npm: 6.9.0
• office-addin-manifest: 1.4.2.

The new syntax in TypeScript 3.8 is not supported.
Could you update the dependent packages?

import type { IObjectWithKey } from "@uifabric/utilities";

  1:14  error  Parsing error: '=' expected  prettier/prettier

Thank you.

main.ts contains exports of classes and functions that can then be imported like so:

import { readManifestFile, ManifestInfo } from 'office-addin-manifest';

Please add validate and xml to this list, so that TypeScript can use the goodness in there as well:

import { validateManifest, ManifestValidation } from 'office-addin-manifest';

Thank you.

Is it possible to combine Blazor and Office Addins? Would like to be able to execute .NET standard libraries from the task pane.

My apologies if this is already listed somewhere, I've been able to find anything in searches.

"Debugging is being stopped...
Debugging has being stopped."

Expect: "Debugging has been stopped"

I'm going through the tutorial to build my first Outlook add-in. I am on Windows 10, and am using the Yeoman generator to create an Angular app:

https://docs.microsoft.com/en-us/outlook/add-ins/quick-start?context=office%2Fdev%2Fadd-ins%2Fcontext&tabs=yeomangenerator

Everything is going well until I get to this step:

Run the following command in the root directory of your project. When you run this command, the local web server will start (if it's not already running).

npm start

If I run npm start, I get this output:

> [email protected] start D:\Office Addin\src\OfficeAddin.Outlook
> office-addin-debugging start manifest.xml

Debugging is being started...
App type: desktop
Enabled debugging for add-in 05c2e1c9-3e1d-406e-9a91-e9ac64854143. Debug method: 0
Starting the dev server... (webpack-dev-server --mode development)
Unable to start the dev server. Error: The dev server is not running on port 3000.
Debugging started.

What am I doing wrong?

Hi

I created a React Word AddIn and want to use something like process.env.ENVIRONMENT. Can you please provide some guidance on how to determine if the code is running locally or in production?

Thank you!
Pascal

This is because xml2js does not preserve comments. Leonidas-from-XIV/node-xml2js#44

When the certificate has less than a day until expiry, the certificate verification step fails, and it adds a new certificate. The next time it tries to verify the certificate, it still sees the old certificate, and creates another new certificate.

This is how you are verifying certificates:

The security find-certificate call finds the first matching certificate, which is the expiring one, even after a new certificate is added.

Expected behavior

The lib/ directory is present in the release packages for all scripts.

Current behavior

Multiple packages fail upon requiring them because they try to import from the 'lib/' directory that is absent in the latest release.

Affected packages are at least [email protected], [email protected], [email protected], [email protected] etc.

They are all packages that were released as part of the latest release AFAIU.

Prerequisites

Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.

• I am running the latest version of Node and the tools
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Expected behavior

by running "npm install eslint-config-office-addins" the latest version of the npm module is installed and works
(all seems to work with version [email protected])

Current behavior

after I run the lint comment via the "npm run lint" command I get this:

[email protected] lint:office [EDITED_PATH] office-addin-lint check

Oops! Something went wrong! :(

ESLint: 6.8.0.

ESLint couldn't find the config "eslint-config-office-addins" to extend from. Please check that the name of the config is correct.

The config "eslint-config-office-addins" was referenced from the config file in "[EDITED_PATH]/.eslintrc.json".

If you still have problems, please stop by https://gitter.im/eslint/eslint to chat with the team.

Steps to Reproduce

follow the instruction in the README.md of this repo: https://github.com/OfficeDev/Office-Addin-Scripts/blob/master/packages/office-addin-lint/README.md

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: OSX Catalina (10.15.6)
• Node version: v10.17.0
• Office version: not relevant
• Tool version: eslint-config-office-addins 1.0.16

Our Office JS Add-in's webpack build creates two separate websites. They both maintain the same set of custom functions, but have different implementations in two different typescript files. We are using the CustomFunctionsMetadataPlugin on each of them to generate the CustomFunctions.associate() calls in the corresponding output js files. However, it looks like when you use the plugin more than once, then you get extra CustomFunctions.associate() calls in your js output. Can this be fixed so only the custom functions found in each typescript file are added to the corresponding js file?

For a custom function which needs to do an async operation, it will need to return a Promise where ResultType is an allowed result type.

Currently only a function that returns ResultType directly is supported, but not Promise.

• update spec to include returning a Promise for non-streaming functions.
• add test cases for returning a Promise from the function
• fix the implementation to allow returning a Promise

Getting the following error in an Angular app.

ERROR in ./node_modules/office-addin-sso/lib/odata-helper.js
Module not found: Error: Can't resolve 'https' in '***\node_modules\office-addin-sso\lib'

I think it is due to the fact that Angular no longer assumes Node modules are available.

For the https://github.com/OfficeDev/Excel-Custom-Functions project, if the version of clean-webpack-plugin is updated to version 3.0.0 in package.json

"clean-webpack-plugin": "^3.0.0",

and the import is updated as in OfficeDev/Excel-Custom-Functions@e02646a,

"npm run build" will not build successfully.

Hi,

I created a started app with Yeoman using [email protected]
Here is the console output:

`npm start desktop

[email protected] start C:\Users\xxx\excel-addin
office-addin-debugging start manifest.xml "desktop"

Debugging is being started...
App type: desktop
Enabled debugging for add-in 05c2e1c9-3e1d-406e-9a91-e9ac64854143. Debug method: 0
Starting the dev server... (webpack-dev-server --mode development)
The dev server is running on port 3000. Process id: 22816
Sideloading the Office Add-in...
Error: Unable to start debugging.
Error: Unable to sideload the Office Add-in.
Error: Unable to delete registry value "C:\Users\xxx\excel-addin\manifest.xml" in key "HKCU\SOFTWARE\Microsoft\Office\16.0\Wef\Developer".
ProcessUncleanExitError: DELETE command exited with code 1:

Erreur�: Erreur�: le syst�me n'a pas trouv� la cl� ou la valeur de Registre sp�cifi�e.`

This error is preventing the debugging from starting. After digging aroud a bit, I think issue lies with the RegistryKey class. The deleteValue function (line 112) is matching the error message to a specific string in english, but my system is returning an error message in french.

If I create the value it is looking for in the registry before starting the debugger I do not have an issue.

I attempted to run the Add-in generator on Linux, but I hit an exception from office-addin-dev-certs that the linux platform is not supported. Is making this compatible with Linux as easy as updating the getInstallCommand, getUninstallCommand, and getVerifyCommand functions with a case for linux? If so, I'd be happy to submit a PR.

If the function return type is not explicitly specified using TypeScript or @returns {type}, the type is always any. It should detect a simple type (boolean, number, string), matrix type (any[][], boolean[][], number[][], string[][]), etc.

    /**
     * @customfunction
     */
    function returnsBoolean() {
      return true;
    }

EXPECTED:

result: {
   "type": "boolean";
}

ACTUAL:

result: { }

In visual studio we have the option to specify a template file that our sideloaded app starts with. With this, the template is hard coded. A flag or environment variable to change this would be awesome.

Hi,

it seems you have accidentally added fs but this is not a package on npmjs, fs is an internal NodeJS module.

https://github.com/OfficeDev/Office-Addin-Scripts/search?q=0.1-security&unscoped_q=0.1-security

See https://nodejs.org/api/fs.html

You might want to remove it using npm uninstall fs.

I'm currently developing an Excel add-in in Windows 10. Since I'm trying to open two instances of the add-in in different ports, I'm trying to start another dev-server in port 44389 by doing

office-addin-debugging start manifest.xml desktop --dev-server-port 44389

but the following output shows up:

Debugging is being started...
App type: desktop
Enabled debugging for add-in 20c008db-10d8-4e87-bed4-29aaa26f673b. Debug method: 0
Starting the dev server... (webpack-dev-server --mode development)
Unable to start the dev server. Error: The dev server is not running on port 44389.
Sideloading the Office Add-in...
Debugging started.

If I run the application with the default port (3000), it works ok.

I currently have a function which is called when the sent button is pressed, so I am able to get the fields I require. The purpose of the add-in is log emails which need to be recorded for financial rules.

What I'm trying to do is add a dialog box when send is pressed asking if they need to log that particular email. I've looked at the dialog samples but they aren't overly helpful for running on Events.

When the MessageSent function is called I've even tried calling a separate dialog box:
function ShowDialog() { var dialog; Office.context.ui.displayDialogAsync('/Dialog.html', { height: 30, width: 20 }, function (asyncResult) { dialog = asyncResult.value; dialog.addEventHandler(Office.EventType.DialogMessageReceived, processMessage); } ); }

Has anyone got this kind of email sending confirmation to work?

Essentially I need this but with different text:

This is a new piece of metadata that is opt-in model, that requires the schema of the function to be included as a new parameter on the function.

Expected behavior

When using office-addin-dev-settings to enable loopback for Edge, expect to set it once and the settings get saved so it does not need to prompt the user for confirmation to set the loopback.

Current behavior

The prompt for enabling loopback confirmation keeps showing up, so when using office-addin-debugging to sideload office during automation, the automation will get paused.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. call ensureLoopbackIsEnabled in code to enable the loopback
2. call npx office-addin-debugging start ... it will prompt again for enabling the loopback

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating System: 1903
• Node version: 12.16.1
• Office version:
• Tool version: [email protected] or above

To repro:
On Windows 10, starting without any .office-addin-dev-certs folder or certs installed, run:
office-addin-dev-certs install
When prompted to install the CA certificate, say "n" for no.

Result:

c:\dev\git\Office-Addin-Scripts\packages\office-addin-dev-certs>node lib\cli.js install
The developer certificates have been generated in C:\Users\adamk\.office-addin-dev-certs
Installing CA certificate "Developer CA for Microsoft Office Add-ins"...
(node:256) UnhandledPromiseRejectionWarning: Error: Unable to install the CA certificate. Import-Certificate : The operation was canceled by the user. (Exception from HRESULT: 0x800704C7)
At line:1 char:1
+ Import-Certificate -CertStoreLocation cert:\CurrentUser\Root C:\Users ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Import-Certificate], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.CertificateServices.Commands.Impor
   tCertificateCommand


    at c:\dev\git\Office-Addin-Scripts\packages\office-addin-dev-certs\lib\install.js:52:19
    at Generator.next (<anonymous>)
    at c:\dev\git\Office-Addin-Scripts\packages\office-addin-dev-certs\lib\install.js:6:71
    at new Promise (<anonymous>)
    at __awaiter (c:\dev\git\Office-Addin-Scripts\packages\office-addin-dev-certs\lib\install.js:2:12)
    at installCaCertificate (c:\dev\git\Office-Addin-Scripts\packages\office-addin-dev-certs\lib\install.js:44:12)
    at Object.<anonymous> (c:\dev\git\Office-Addin-Scripts\packages\office-addin-dev-certs\lib\install.js:38:19)
    at Generator.next (<anonymous>)
    at fulfilled (c:\dev\git\Office-Addin-Scripts\packages\office-addin-dev-certs\lib\install.js:3:58)
(node:256) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:256) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The test will frequently fail. It may succeed when re-run but the cause of the timing problem leading to the failure needs to be fixed.

  1) test javascript file as input
       js test
         basic test:

      AssertionError [ERR_ASSERTION]: json file not created
      + expected - actual

      -false
      +true

      at Context.<anonymous> (test\src\test.ts:65:20)
      at Generator.next (<anonymous>)
      at fulfilled (test\src\test.ts:3:58)
      at process._tickCallback (internal/process/next_tick.js:68:7)

This file should be removed. It seems that it was pushed erroneously by git.

It looks like the loader doesn't accept spaces in the path.

Part 1.

npm run lint

[email protected] lint {path}*My Outlook Add-in*
office-addin-lint check

internal/modules/cjs/loader.js:800
throw err;
^

Error: Cannot find module '{path}*My*'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
at Function.Module._load (internal/modules/cjs/loader.js:690:27)
at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
at internal/main/run_main_module.js:17:11 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] lint: office-addin-lint check
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! {profile}\AppData\Roaming\npm-cache_logs\2020-02-06T15_14_32_020Z-debug.log

Part 2.

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'lint'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prelint', 'lint', 'postlint' ]
5 info lifecycle [email protected]prelint: [email protected]
6 info lifecycle [email protected]lint: [email protected]
7 verbose lifecycle [email protected]lint: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]lint: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;{path}\My Outlook Add-in\node_modules.bin;C:\Python27;C:\Python27\Scripts;C:\Program Files (x86)\Embarcadero\Studio\20.0\bin;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl;C:\Program Files (x86)\Embarcadero\Studio\20.0\bin64;C:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl\Win64;C:\Program Files (x86)\Embarcadero\Studio\19.0\bin;C:\Users\Public\Documents\Embarcadero\Studio\19.0\Bpl;C:\Program Files (x86)\Embarcadero\Studio\19.0\bin64;C:\Users\Public\Documents\Embarcadero\Studio\19.0\Bpl\Win64;C:\Program Files (x86)\Borland\Delphi7\Bin;C:\Program Files (x86)\Borland\Delphi7\Projects\Bpl;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Symantec.cloud\PlatformAgent;C:\Program Files\Microsoft SQL Server\130\Tools\Binn;C:\Program Files\Microsoft\Web Platform Installer;C:\Program Files\dotnet;C:\WINDOWS\System32\OpenSSH;C:\Program Files\TortoiseGit\bin;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn;C:\Program Files\Microsoft SQL Server\130\DTS\Binn;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Program Files\Git\cmd;{profile}\AppData\Local\Microsoft\WindowsApps;{profile}\AppData\Local\atom\bin;{profile}\AppData\Local\Microsoft\WindowsApps;{profile}\AppData\Roaming\npm;{profile}\AppData\Local\Programs\Microsoft VS Code\bin;{profile}\AppData\Local\GitHubDesktop\bin;{profile}\AppData\Local\Programs\Fiddler
9 verbose lifecycle [email protected]lint: CWD: {path}\My Outlook Add-in
10 silly lifecycle [email protected]lint: Args: [ '/d /s /c', 'office-addin-lint check' ]
11 silly lifecycle [email protected]lint: Returned: code: 1 signal: null
12 info lifecycle [email protected]lint: Failed to exec lint script
13 verbose stack Error: [email protected] lint: office-addin-lint check
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:210:5)
13 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:210:5)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid [email protected]
15 verbose cwd {path}\My Outlook Add-in
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "lint"
18 verbose node v12.13.1
19 verbose npm v6.12.1
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] lint: office-addin-lint check
22 error Exit status 1
23 error Failed at the [email protected] lint script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

The npx office-addin-dev-certs uninstall command should also delete the cert files and remove the .office-addin-dev-certs folder if it is empty.

If you have a function like "add10" and call parseTree with it, it will generate the proper result:

/** @CustomFunction */
function ADD10(x: number): number {
  return x + 10;
}

    [
        {
            "javascriptFunctionName": "ADD10",
            "nonCapitalizedFullName": "TestNamespace.ADD10",
            "status": "good",
            "errors": [],
            "metadata": {
                "id": "TESTNAMESPACE.ADD10",
                "name": "TESTNAMESPACE.ADD10",
                "parameters": [
                    {
                        "name": "x",
                        "type": "number"
                    }
                ],
                "result": {
                    "type": "number"
                }
            }
        }
    ]

But if you were to capitalize the function to "ADD10", it throws an error!

"@customfunction tag specifies a duplicate name: ADD10 (1,1)"

The issue was found by David Chestnut in Script Lab: OfficeDev/script-lab#709

Could you please fix the package and then update script lab? You can check it in directly into branch "fix-709" (https://github.com/OfficeDev/script-lab/tree/fix-709), where I added a test that currently fails due to this issue.

OfficeDev/generator-office#462

MacOS still appears to have the problem of getting
$ office-addin-debugging stop manifest.xml env: node\r: No such file or directory error Command failed with exit code 127.
The way to resolve the issue locally is to change the line ending in .bin -> office-addin-debugging from CRLF to LF.

Originally posted by @jpshankle in #160 (comment)

If Yo Office is used to create a project for Outlook, the "npm start" command should handle the fact that Outlook cannot sideload more gracefully. It can ensure the dev server is running, and then provide instructions for the user to sideload manually. See https://docs.microsoft.com/en-us/outlook/add-ins/sideload-outlook-add-ins-for-testing.

Instead of the developer having to explicitly put the calls to CustomFunctions.associate("ID", func), it would be nice to have the webpack plugin be able to emit this.

The way to do this is to tap into the render event of the moduleTemplates so that for the "functions" module, after the code is rendered, it can add the additional lines to add the CustomFunctions.associate() calls.

Prerequisites

Node: v12.16.3

Current behavior

When developing an Excel add-in, office-addin-debugging continuously throws the following exceptions:

ApplicationInsights:Sender [
  'Ingestion endpoint could not be reached 20 consecutive times. There may be resulting telemetry loss. Most recent error:',
  Error: socket hang up
      at connResetException (internal/errors.js:608:14)
      at Socket.socketOnEnd (_http_client.js:453:23)
      at Socket.emit (events.js:322:22)
      at endReadableNT (_stream_readable.js:1187:12)
      at processTicksAndRejections (internal/process/task_queues.js:84:21) {
    code: 'ECONNRESET'
  }
]

ApplicationInsights:Sender [
  'Not saving data due to max size limit being met. Directory size in bytes is: 50000175'
]

Is there any way to either disable Application Insights or squelch this error? In addition, what directory is the error message referring to? I have not been able to find any documentation on these issues.

When i run npm run lint, i get the following message

> office-addin-lint check


Oops! Something went wrong! :(

ESLint: 6.8.0.

No files matching the pattern "src/**/*.js" were found.
Please check for typing mistakes in the pattern.

I'm writing a taskpane for Excel with Typescript and React.
I haven't changed anything on the eslint configuration.

I'm have this on my package.json

 "office-addin-lint": "^1.0.21",

Thanks.

See OfficeDev/office-toolbox#37 for more details.

In a office add-in development environment when executing the command : npm run dev-server

console output:

> [email protected] dev-server C:\Users\Edwin Veroes\Documents\outlook-addin-reactjs
> webpack-dev-server --mode development

The developer certificates have been generated in C:\Users\Edwin Veroes\.office-addin-dev-certs
Installing CA certificate "Developer CA for Microsoft Office Add-ins"...
Error: Unable to install the CA certificate. Import-Certificate : A positional parameter cannot be found that accepts argument 'Veroes\.office-addin-dev-certs\ca.crt'.
At line:1 char:1
+ Import-Certificate -CertStoreLocation cert:\CurrentUser\Root C:\Users ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Import-Certificate], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.CertificateServices.Commands.ImportCertificateCommand


    at C:\Users\Edwin Veroes\Documents\outlook-addin-reactjs\node_modules\office-addin-dev-certs\lib\install.js:58:19
    at Generator.next (<anonymous>)
    at C:\Users\Edwin Veroes\Documents\outlook-addin-reactjs\node_modules\office-addin-dev-certs\lib\install.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (C:\Users\Edwin Veroes\Documents\outlook-addin-reactjs\node_modules\office-addin-dev-certs\lib\install.js:4:12)
    at installCaCertificate (C:\Users\Edwin Veroes\Documents\outlook-addin-reactjs\node_modules\office-addin-dev-certs\lib\install.js:47:12)
    at Object.<anonymous> (C:\Users\Edwin Veroes\Documents\outlook-addin-reactjs\node_modules\office-addin-dev-certs\lib\install.js:41:19)
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\Edwin Veroes\Documents\outlook-addin-reactjs\node_modules\office-addin-dev-certs\lib\install.js:5:58)

this is caused because the resultant .js of the file ./packages/office-addin-dev-certs/src/install.ts outputs in the line 21 for the command for windows the variable "caCertificatePath" without surrounding quotation marks.

Was able to work around this by adding simple quotation marks to the resultant .js file but changes need to be done to the .ts file in your repo.

See OfficeDev/Excel-Custom-Functions#168

All of the tasks are failing for me. I'm wondering if it's my scenario and it's an edge case.

PS Z:\jason_r On My Mac\source\ToucanOfficeAddIn> npm run start

[email protected] start Z:\jason_r On My Mac\source\ToucanOfficeAddIn
office-addin-debugging start manifest.xml

npm : 'office-addin-debugging' is not recognized as an internal or external command,
At line:1 char:1

• npm run start

•   + CategoryInfo          : NotSpecified: ('office-addin-d...ternal command,:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
  
  

operable program or batch file.

Even though I have done an npm install with no errors the tools are still being seen as unknown commands.

I am running a VM instance of Windows on a mac, and I am running the project from a shared drive from the host.