Exam MS-600 topic 5 question 4 discussion

sideload your add-in to test it

Debug your add-in: 1. To debug your add-in by using Office on the web: Run the project on localhost and sideload it to a document in Office on the web. For detailed sideloading instructions, see Manually sideload Office Add-ins on the web. 2. Open the browser's developer tools. This is usually done by pressing F12. Open the debugger tool and use it to set breakpoints and watch variables.

You want to debug, so you want to make temporary changes and test them, sideloading seems to be the way to go. https://docs.microsoft.com/en-us/office/dev/add-ins/testing/sideload-office-add-ins-for-testing If you're using Visual Studio to develop your add-in, the process to sideload is similar to manual sideloading to the web. The only difference is that you must update the value of the SourceURL element in your manifest to include the full URL where the add-in is deployed.

C is correct. You need to upload the manifest to SharePoint app catalog https://docs.microsoft.com/en-us/office/dev/add-ins/testing/debug-add-ins-in-office-online

Sideload the add-in : https://docs.microsoft.com/en-us/office/dev/add-ins/testing/sideload-office-add-ins-for-testing

Answer C is correct. "Although you can sideload add-ins from Visual Studio to Office on the web, you cannot debug them from Visual Studio. To debug you will need to use the browser debugging tools. For more information, see Debug add-ins in Office on the web." https://docs.microsoft.com/en-us/office/dev/add-ins/testing/sideload-office-add-ins-for-testing

B) I'd assume that, if the user reports a bug ,it is because the add-in is in production already so there is not need to publish the manifest twice.

Actually in most Youtube Videos they show that Add-Ins are debugged by Sideloading