Support a Debugger for Mac desktop clients
Supporting the Chrome Debugging Protocol on the embedded Webkit instance that runs in Office for Mac would make something like github.com/Microsoft/vscode-chrome-debug will be a viable debugger on the Mac.
There maybe alternatives to Chrome Debugging Protocol that I'm unaware of that can more easily be supported by VS Code. Either way, we are simply asking for a full fledged debugger (unlike Vorlon.js) that can plug in to the running add-in and set breakpoints, explore values etc.
João Rocha commented
Making it possible to use Chrome's Developer Tools would be a great help to debug Office Add-ins.
This would definitely make the development easier, and it would make our developers happier.
Please consider to support Chrome!
Dalibor Grudenić commented
This is currently supported and works very well on Mac.
Lance Austin commented
Yeah, I would add to this. There are two big challenges that I have faced thus far when developing Office Add-in's.
#1 - The gap between the VSTO and Add-in API's
#2 - The developer tooling
I know the team is continuing to address the gap in API's between VSTO and the Add-ins and this will continue to improve over time. The area I haven't seen much progress or discussion is around developer tooling.
I would extend Sameera's request to be broader than just Mac and be more about improving the overall Developer Experience. From my understanding the main ways to debug the office clients today are Vorlonjs and Edge Debug Tools (assuming you have windows 10). I do development on both my Mac and PC (Windows 8.1).
Vorlon is ok and is better than nothing but it is very buggy and doesn't seem to like modern web tools like browser sync. Based on the Github Repo it doesn't seem to be getting any love either.
Also, I'm an Angular 2 developer so it would be really great to leverage the developer tools that they provide such as the Augury Chrome Extension. Therefore, being able to attach the Chrome Debugger would be ideal on both Mac and PC.
A lot of times what I end up doing is opening it on Office Online which is much better but since it runs in an iFrame I still end up not being able to use extensions like Augury.
Overall, the point I'm trying to make is that the Office add-in model is awesome in concept but without a better developer experience it will continue to frustrate users. I'm fully committed to adopting the new add-in model so please let me know how I can help and if I can add additional color around these areas!