I am creating an Outlook Add-in using Office js libraries. I was using the option to attach the debugger to debug my javascript application. But it seems that after an Outlook update the option is no longer available. I have tried reinstalling Office but dit not help. Also i created a new Add In with the default functionality and this has no option to attach the debugger. When i click with the right mouse I see no options. Do i have to enable it in some new way ? Has somebody else seen this problem ?
Beginning with Office 365 version 16.0.11629 and Windows 10 version 1903, Office Add-ins running on Office 365 for Windows will use a Microsoft Edge WebView as the runtime.
The Microsoft Edge WebView performs much better than Internet Explorer and features enhanced compliance with modern browser standards including support of the full set of HTML 5 and ECMAScript 2015+.
We recommend that you download the Microsoft Edge DevTools Preview for debugging.
link
Related
I am trying to write my first JavaScript Word add-in using Visual Studio Code. As a basis I used the Simple Word Add-in example provided by Microsoft. The example puts all JavaScript code in the commands.html file. I would like to put my code in the separate commands.js file, and use the Word Javascript API instead of the Common API. But with most changes Word just does not respond and I can't see what's happening at this stage.
I have installed the Microsoft Office Add-in Debugger Extension for Visual Studio Code. All examples that I have seen are task pane add-ins, and I was able to attach a debugger to those examples. Is there any way to debug a command add-in (without a task pane)?
Unfortunately the Microsoft Office Add-in Debugger Extension for Visual Studio Code will not work for debugging commands. In order to debug commands, your best bet is to upload your add-in manifest to Office Online, view it in Edge or Chrome and use the DevTools (F12). You should be able to add the add-in project source in the DevTools and just set breakpoints in the commands.
If you are running the Edge Chromium (which I don't think you are based on the fact that Microsoft Office Add-in Debugger Extension worked for taskpane add-ins), debugging commands can all be done in VS Code.
I am using Outlook 2013 application to test the Outlook add-in I am creating. At the moment, when I click a button on my add-in, it is just saying App Error and I don't know what is causing it.
Is there a way for me to debug my code to see where the error is coming from?
I depends on your windows version, have a look here.
For Windows 10:
Launch the F12 development tools that corresponds to your version of Office:
For the 32-bit version of Office, use C:\Windows\System32\F12\IEChooser.exe
For the 64-bit version of Office, use C:\Windows\SysWOW64\F12\IEChooser.exe
I am working on an Outlook add in and it works fine for all the browsers. However it does not work with Outlook 2016. Initially it worked with Mac, but now it doesn't seem to work with either. It seems like the Office.initialize is never called?
I've searched and tried things for hours but nothing works. Comparing my manifest and initialization to others, I seem to have essentially the same code.
I used the yeoman generator and I am using Office UI Fabric React as my framework. Really at a loss at this point, wondering if anyone has any suggestions or a way to see if any errors are thrown in the Outlook Desktop app?
Update
After much searching and trying things, and starting from scratch, it seems that the add-in stops working as soon as I start using the Office-JS API. Specifically I'm getting the userProfile and the to, from, cc fields from the email Office.context.mailbox.item.
Still unable to find a solution.
When using Office-JS APIs, be sure to call those APIs only after Office.initialize has been called.
Beyond that, there are a few options for debugging add-ins in Outlook 2016. The last section on this page describes how to attach the Visual Studio debugger to the process running the add-in. Be sure to enable Script Debugging in IE options.
There also are a couple of newer options for debugging Office add-ins:
Launch the Visual Studio debugger from a task pane (in Outlook, I right-clicked on the task pane to see this option)
On Windows 10, debug using F12 tools (simple to use, and doesn't require Visual Studio)
For an Outlook add-in running in OWA, just open F12 Developer Tools in any web browser.
I am trying to record a Web Performance Test using the Web Test Recorder 12.00 plugin that comes with VS 2013.
This is what I get when the toolbar opens:
As you can see the buttons are greyed out and disabled.
I have followed this work around, but without any luck.
Are there any restrictions for this tool?
Is that a known issue?
I have disabled the Web Test Recorder Helper Add-on and restarted IE, and enabled Add-on again. And it worked for me.
I'm brand new to performance testing, and ran into the same problem using VS 2015, Win 7, IE11. The culprit in my case was an IE11 add-on called "Office Document Cache Handler". Microsoft was the one that created the add-on (which I find rather frustrating), but hopefully this helps someone down the road.
This is a known issue. Been around for years. Unfortunately, Microsoft has no sure fire method to resolve it.
I am currently having this issue and would really like to find a supported solution, as I will not be shelling out the big bucks for 2013 Ultimate with this issue stopping me from using it for web load testing.
Issues with this have been under discussion on msdn since at least 2007: http://blogs.msdn.com/b/mtaute/archive/2007/11/09/diagnosing-and-fixing-web-test-recorder-bar-issues.aspx
3rd party edit
The link above contains different "fixes" depending on the OS and the VS version. The version 2013 was not mentioned. But to include at least some information the following quotes are extracts from Michael Taute (MSFT) post:
VSTS 2005: Vista:
Recorder bar displays, but the controls are disabled.
Fix: Webtest recording using VS 2005 on Vista only works when running in
elevated mode. [When launching VS 2005, right click the icon and choose to
run as administrator]
or
VSTS 2005, 2008: Windows 2003/Vista:
Recorder bar comes up, but the controls are disabled.
Fix: the web test recorder bar does not work with IE enhanced security
enabled. (VSTS 2008 will actually display an error message telling you
this) IE enhanced security can be removed from within the Control
panel / Add Remove Programs / Windows Setup
or
VSTS 2005, 2008, 2010 Beta 1: Windows 7:
When launching the recorder, the recorder bar does not appear
Fix: The Windows 7 security model is slightly different than previous
versions of windows. (go figure :)
To get the recorder to show up, you’ll have to run Visual Studio
in elevated mode.
I've got TWO addons:
Microsoft Web Test Recorder 12.0 Helper (Publisher = "Microsoft Corporation")
Web Test Recorder 12.0 (Publisher = "Not Available")
Both of them should be enabled, otherwise recorder toolbar is grayed out or not displayed at all. I'm running Windows 10 and VS 2013 update 5.
Instead of adding 'WebAndLoadTestProject' to existing solution, Start with new solution as given in below steps.
Open Visual studio in 'Run As Administration' mode
Create new project -> Test -> add 'Web performance And Load Test Project'.WebAndLoadTestProject
This opens IE browser with record button enabled state.
I have created a simple plugin and installed it on my outlook (for windows). It works fine. However i want to know - can I install the same plugin on outlook (for Mac)? If so, Please guide. Thanks!!
No, you can't. Office/Outlook for Mac doesn't support add-ins. The COM technology (on which Office add-ins are based) is for Windows only.
The only possible option is to develop a VBA macro instead.