Not able to debug Outlook Web add-in in new Outlook (Desktop)

Not able to debug Outlook Web add-in in new Outlook (Desktop)
1

Upvotes

Upvote

 Aug 08 2023
4 Comments (4 New)
New

In current Outlook version (Desktop),

adesai5011_1-1691488084026.png

when opening our Outlook Web add-in, we can use "Inspect" option (by performing right click from the mouse) in the web add-in taskpane (right side pan) as below. BTW, our Outlook Web add-in is working fine in the current Desktop Outlook,

 

adesai5011_0-1691487883620.png

 

When opening the same Outlook Web add-in in New Outlook (Desktop),

adesai5011_2-1691488293140.png

Our Outlook Web add-in not working in the New Outlook (Desktop) and throwing some error and this "Inspect" element is not showing when we will do right click in the web add-in taskpane (right side pan) and we are not able to debug our Outlook Web add-in regarding what error/exception occur in our Outlook add-in,

adesai5011_3-1691488368119.png

 

Comments
Copper Contributor

Hi all, any update on this request? We are not able to use our Outlook web add-in further in new Outlook. Please review this asap.

Copper Contributor

We too are having this issue. It is very hard to debug Outlook apps in the new version of outlook when we can't see the inspect tools.

Brass Contributor

Thanks for your timely response @daviddykstra, as I just learned of a solution for this last week directly from the Outlook dev team! With the New Outlook closed, run this from the command prompt window:

olk.exe --devtools

This will start the New Outlook with DevTools open and ready to go! This even provides the advantage of being able to see console output when a Task Pane or Office JS Dialog loads, where before you had to open it first, then launch DevTools, then refresh the page to reload the add-in again. However, if you close DevTools when you launch the New Outlook with this command, you will have to run the command again to bring back DevTools - but it will start a second instance of the New Outlook.

 

Hope this helps!

Copper Contributor

As a side note, I've done all of my development against outlook.office.com because it's much easier to debug. The smart alerts run in the same context as the outlook application, so you can easily set breakpoints on it.