Skip to content

Commit 4db8f74

Browse files
authored
[All Hosts] (testing) two fixes for sideloading unified manifest (#5101)
* [All Hosts] (testing) two fixes for sideloading unified manifest * typo
1 parent 38d42b2 commit 4db8f74

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/testing/sideload-add-in-with-unified-manifest.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Sideload Office Add-ins that use the unified manifest for Microsoft 365
33
description: Test your Office Add-in on Windows by sideloading.
4-
ms.date: 02/26/2025
4+
ms.date: 03/27/2025
55
ms.localizationpriority: medium
66
---
77

@@ -31,11 +31,15 @@ Use the process described in [Sideload with a system prompt, bash shell, or term
3131
1. Press F5. The project builds and a Node dev-server window opens. This process may take a couple of minutes and then the desktop version of the Office application that you selected opens. You can now work with your add-in. For an Outlook add-in, be sure you're working in the **Inbox** of *your Microsoft 365 account identity*.
3232
1. To stop debugging and uninstall the add-in, select **Run** | **Stop Debugging** in Visual Studio Code. Closing the server window doesn't reliably stop the server and closing the Office application doesn't reliably cause Office to unacquire the add-in.
3333

34+
> [!NOTE]
35+
> If the preceding step seems to have no effect, uninstall the add-in by opening a **TERMINAL** in Visual Studio Code, and then complete the uninstall step — the *last* step — of the section [Sideload with a system prompt, bash shell, or terminal](#sideload-with-a-system-prompt-bash-shell-or-terminal).
36+
3437
## Sideload with a system prompt, bash shell, or terminal
3538

3639
1. First, *make sure the Office desktop application that you want to sideload into is closed.*
3740
1. Open a system prompt, bash shell, or the Visual Studio Code **TERMINAL**, and navigate to the root of the project.
3841
1. The command to sideload the add-in depends on when the project was created. If the "scripts" section of the project's package.json file has a "start:desktop" script, then run `npm run start:desktop`; otherwise, run `npm run start`. The project builds and a Node dev-server window opens. This process may take a couple of minutes then the Office host application (Excel, Outlook, PowerPoint, or Word) desktop opens.
42+
1. For an Excel, PowerPoint, or Word add-in, there is an additional step: select the **Add-ins** button on the **Home** ribbon. On the flyout that opens, select the add-in. This completes the installation.
3943
1. You can now work with your add-in.
4044
1. When you're done working with your add-in, make sure to run the command `npm run stop`. Closing the server window doesn't reliably stop the server and closing the Office application doesn't reliably cause Office to unacquire the add-in.
4145

0 commit comments

Comments
 (0)