At one point I was able to see our Outlook add-in app in the target options in f12 devtools for troubleshooting, but sometime last month it stopped showing up there. My colleagues are stumped, and I can't find much online in the way of troubleshooting.
I tried checking my Windows version and Outlook version against others who can see it in their devtools, but we're all on Windows 10 enterprise v1803, Outlook v1910, and IE 11. I've tried many things over the month since this happened like rebooting my PC, making sure I have the latest updates from IT, refreshing the options, running some commands I found online for targeting the right browser for devtools, etc. No change.
Another peculiar thing is that I'm seeing some completely different things in the Add-in than they are, like button alignments and div widths and such. I had our dev environment looking perfect on my end, but when a few people on the team screenshared with me there were a number of styling issues I can't reproduce. Even weirder, nobody experiences these issues in O365, it's just the desktop Outlook app on our Windows machines.
Any ideas on how to troubleshoot this would be very greatly appreciated.
Steps I take to produce the issue:
Click on manifest icon for our app in Outlook ribbon. App loads in the sidebar.
Open F12 devtools (both 32 and 64 bit for good measure from the System32 and SysWOW64 directories).
App is not in the target list. Click refresh, still not in the list.
FYI, any IE 11 windows I have open show up there, just not my app.
Starting in Windows 10 version 1903, the latest version of Office will use Edge WebView instead of IE to render add-ins. Edge WebView requires a different debugger (not the F12 debugger) called Microsoft Edge DevTools. You can find out more about it here.
Related
Recently, opening Outlook 2019 is triggering a Edge browser announcing "Your Organization is moving to Microsoft Edge"...with about 6 or so following "Nexts"...I cannot seem to surpress it (we use Google Chrome as default). That aside, for a few, a blank white Edge window opens instead, which I presume is the same thing but failing to display the content...I cannot get it to stop, even by launching the URL from a working machine and running through the "wizard"...seems like blowing away Edge or Windows profile might be the only solution (or something else common to them...they are all similar machines, same MDT image load)...they are virtual machines though (come to think of it as I type this). Our others are physical PCs.
I ran into the same issue. When Outlook 2019 launches it opens a white Edge window that is unresponsive. The issue is triggered only when a user signs into Edge to setup account sync. If there is no user sign in then issue does not occur.
After many hours of troubleshooting the issue was resolved by setting the following registry entry:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Edge\IEToEdge
RedirectMode 2
When a Windows 10 computer wants to share some of its screens using webrtc protocol (firefox navigator), a list of the windows that can be shared appears. In this list, only "normal" applications appears, not the one related to "apps". By example, spotify window appears, but OneNote window is not listed.
It seems (?) webrtc screen share is not compatible with UWP apps.
Knows someone a way to share the screen of an app via webrtc ?
Note: following link allows to reproduce this issue:
https://mozilla.github.io/webrtc-landing/gum_test.html
you do not need share anything, just push "window" and see the list of windows that appears.
I believe Chromium (the open source version - not sure about Chrome) faces the same problem as UWP requires to use a new Win 10 API which shows it's own window selector. And then obviously that selector doesn't work on other problems. So it's a common problem on Win 10, with no known good solution as far as I can tell.
I'm the author of a Windows application that's been around for years. The app uses the wxWidgets UI library. For the newest version, we upgraded to the Microsoft c++ compiler in Studio 10 and to the latest Windows SDK library. We did not change much else in the app. Now, several users have reported that after a period of time running the app, the menus go crazy. All of the users reporting the problem are running on Windows XP. The menus either get huge, filling the screen, and have a giant italic font with strikethroughs. Or they get really small, so that the only thing shown are up and down arrows, suggesting the rendering code thinks the screen real estate is too small to display anything else.
You can find example screen shots here:
Once the menus go crazy, all menus are affected, except the standard Windows and MDI menus. The only way to recover is to restart the app.
The code in the app and wxWidgits is a thin layer on top of the standard Windows API. Once the menus are created, afaik Windows manages the rendering.
Any ideas what's going wrong?
When I first installed Windows 8 (64 bit, Pro version, with Media Player), the IE icon on the Start screen launched the Metro / Modern / Windows Store / whatever version of IE.
But somewhere along the line, it no longer does so. It launches the traditional IE desktop version.
Any suggestions how to get things back to normal?
Side questions: I haven't done any spelunking on Windows 8. Any tips for the following questions would be appreciated...
What are the relevant file locations for various "Metro" apps (both Microsoft and 3rd party)? I know about C:\Windows\SysWOW64\WinMetadata for .winmd files. C:\Windows\WinStore seems almost useless. What else is worthwhile looking at?
Ditto for registry entries
What's hidden where? I assume that apps have NTFS permissions set so that, even as an Administrator (and with doing a Takeown) I can't even see certain system/app-related things.
Where is the Start Screen located? Suppose I wanted to write a program that lists the Start Screen icons, their captions, etc
And any other internals info of this ilk would be appreciated.
Thanks.
Go to Internet Options, Programs tab and in the Opening Internet Explorer section disable the ckeckbox Open Internet Explorer Tiles on the desktop.
Greetings.
We are having some wierd behavior in firefox with silverlight. We have tried everything and I am hoping for some more ideas. Below is the behavior
Install firefox (3.6.12) and silverlight (4.0.50917.0). The versions there are locked and not controlled by us and on all our users machines.
Visit our silverlight application (also tried simple application with just a background)
Instead of seeing our application, you see "Get Microsoft Silverlight"
-- (about:plugins reports silverlight 4.0.50917.0 installed and enabled)
Visit site in IE, app works
Install or uninstall any plug-in (tried Firebug and IETab2)
After install, click "Restart" when prompted
After FF restarts, silverlight works as expected
Close firefox and reopen.
Once again, silverlight is broken
Any ideas? We tried the CWDIllegalInDllSearch entry in the registry to no avail. Please help!
I think it is a problem with Firefox that has been fixed with Version 3.6.14. See this BugReport on Bugzilla. A memory leak in prior versions, cause some problems in the Silverlight detection script of Firefox.
I can only suggest to update Firefox to version 3.6.14. But before i would try it in a local test environment to check if its really a bug in Firefox.
Update:
It seems to be a general problem with Firefox 3.6.x, cause some users report the same error as your with higher versions than 3.6.14. See here and here.
The only thing that springs to mind is disabling the plugin-container
In Firefox address bar type about:config
Read the warning, choose your preference to always remind you or not and accept
In the search bar of the config options now type: npctrl
You should then see the entry: dom.ipc.plugins.enabled.npctrl.dll
Change the value from true to false (simply double-clicking will change this for you)
Restart Firefox
EDIT
There is another workaround which is to disable then re-enable silverlight plugin. Rather than re-isntalling.