Having an issue with debugging an Office Word add-in using F12. Up until lately, it was working fine, but then my company enforced a Windows update and I started having problems. F12 does not appear to find any programs running. I'm using Windows 10 (64bit), Adding an image for reference.
Thanks
Related
Please help me with the following issue.
I developed an Outlook add-in that works great on the following platforms:
Mac os
Windows 10
Windows 8.1
However, a client of mine installed it on Windows Server 2016 with Office 2019 and it doesn't seem to work. It stops at the loading screen. I thought that the old Internet Explorer was the reason, but I tried it in the online Outlook website in Internet Explorer and it worked great. The most annoying issue is that whenever I try to open the debugger from Outlook, it won't work / won't open. I don't know why.
Do you know of any possible reasons that might explain the plugin not working in Outlook but working in the web version? Please help
The problem:
I have a feature for a Microsoft Outlook web add-in which works fine in Office 365 Outlook, but when I test the same feature on Outlook for Mac or Outlook for Windows, the same feature doesn't work. The web add-in still installs fine on Outlook for Mac, it's just that there is a discrepancy between the behavior I am seeing on Office 365 Outlook and Outlook for Mac (this is also true when testing on Outlook for Windows, which has the same behavior as the Mac version).
What I've tried (Mac): I've tried running defaults write NSGlobalDomain WebKitDeveloperExtras -bool true as suggested from this answer and defaults write com.microsoft.Outlook OfficeWebAddinDeveloperExtras -bool true as suggested here and have an option to View Source which opens the HTML source in what appears to be a TextEdit window, but I'm still unable to inspect element in order to see any errors.
What I've tried (Windows):
I've tried using the VSCode Debugger Extension for Office Add-Ins to try to attach the debugger to Outlook for Windows, but keep running into this 'Error processing attach' error.
Additional Notes:
On Mac, I'm running Microsoft Outlook for Mac version 16.43 on MacOS Catalina version 10.15.6 and on Windows I'm running Outlook on Windows 10 Pro version 1909 inside a VM.
My understanding is that while debugging web add-ins for Word, Excel, and PowerPoint are all pretty well supported, debugging add-ins for Outlook on Mac or Windows is somewhat limited at the moment. Has anyone had success in debugging Outlook web add-ins running on Outlook for Mac and/or Windows?
For Outlook for Mac, we think this is specific to the Mac App Store build of Office, which currently doesn't support those flags. To workaround this, you will need to get a non App Store build. You can get one by signing up for the developer program and getting a tenant: https://aka.ms/o365devprogram. (similar issue: https://github.com/OfficeDev/office-js/issues/506)
For Outlook for Windows, we suggest attaching a debugger. Instructions for how to attach a debugger can be found here. Note that there is a different debugger for add-ins that run in Edge and IE.
just starting to look at the Cordova tools for Visual studio.
Creating a blank Cordova probject, I am able to run (F5 debug), for Android and IOS (emulators), and also x86 windows, but for either Any CPU or x64 I get the following error..
The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.
So I have seen mentioned elsewhere that VS (32 bit) needs to run the above for 64 bit debugging. I have no problems running and debugging a classic desktop WPF.
I have tried disabling both my firewall (Zone Alarm) and any antivirus (Avast), but made no difference.
Anyone have any ideas what the problem could be here (or how to diagnose)
Thanks in advance for any help!
I have this same problem. I use the same applications as you do, Zone Alarm and Avast. If I try to debug and get that error, disabling or stopping the programs do not help. You need to close VS and restart it with the offending apps already disabled, then you'll be able to continue.
I stumbled across this question because I am looking for a way to keep from doing this.
Visual Studio 2013 for Desktop is displaying incorrectly. When I open the program, it displays correctly but upon moving my cursor over links or images inside of the interface, they either expand to fill the whole window or the line itself blurs.
I'm running Windows 8.1. I've run it in compatibility mode for XP, Vista, and 7. I've run as administrator. I've reinstalled and repaired. This error is easily reproducible and has occurred over the course of 3 days.
Any help would be appreciated.
Can only guess that your video card vendor happens to maintain a bad driver (or Windows Update pushed a bad version to your machine).
http://support.microsoft.com/kb/2894215
The workaround is to disable hardware graphics acceleration and test again.
I open Internet Explorer 9: i type browse to Google the page load and as it finishes loading the (Tab) Hangs i cant click any links or do any thing, however i can open new tab and type in another site while the other tab is hanging but once i type any site in the new tab it hangs too and so on!
the internet explorer 9 64bit works fine.!
here is what i tried to do:
Turned off Internet Explorer 9 Feature from "Turn on/Off Features"
in control panel, then turned it on, didn't fix the problem.
downgraded to internet explorer 8, and same issue happened in IE8
too !!!. so i upgraded back to IE9 (issue remains).
Switched to Software rendering, (didn't fix problem).
Updated my graphics card to latest driver.
Opened IE9 with no Adds on.
Disabled all adds-on
all this didn't fix the problem!
i need to make it work because i need to do UI Test Automation by Visual studio 2010, and i cant get it to work for Fire-Fox v13 i guess its not supported.
any one faced this problem before and know how to fix it ?
im using Windows 7 64bit
If you have access to and can install VS2010 Feature Pack 2, I believe it supports running coded ui tests in Firefox. There is information on that At MSDN, however, that page recommends Firefox 3.5 or 3.6.