My Excel add in with custom functions using a shared runtime was happily chugging along with the IE11 webview, until about a week ago when it stopped working because it started running only on the Edgium webview.
I think the documentation still says the expected webview is IE11 in the shared runtimes page, but the webviews page could be interpreted as saying it's the edge2 webview.
Did anybody else see the same effect? I mean, that's great if it works (My add in has other problems now, and I can't fully test), I just didn't expect it.
It is a feature. See this note from the article Browsers used by Office Add-ins
If your add-in includes the <Runtimes> element in the manifest, then it will not use Microsoft Edge with the original WebView (EdgeHTML). If the conditions for using Microsoft Edge with WebView2 (Chromium-based) are met, then the add-in uses that browser. Otherwise, it uses Internet Explorer 11 regardless of the Windows or Microsoft 365 version. For more information, see Runtimes.
Related
I have developed an Office add-in for Excel and would now like to test it under production conditions before it is deployed and published in AppSource.
Is there any way to test the add-in under production conditions? The only thing I have found so far is the ability to do this via sideloading (https://learn.microsoft.com/de-de/office/dev/add-ins/testing/test-debug-office-add-ins#sideload-an-office-add-in-for-testing). But that is not a real test environment for me. Are there any other possibilities?
Sideload is our recommendation to test your add-in before you do public publish.
If you plan to publish your add-in to AppSource and make it available within the Office experience, make sure that you conform to the Commercial marketplace certification policies.
https://learn.microsoft.com/en-us/legal/marketplace/certification-policies
After you submit, A validation test will be conducted.
please pay attention to following areas:
Add-ins must follow design guidelines without impeding the customer
experience within the host application.
Add-ins must be compatible
with all versions of Internet Explorer 11 and later, and the latest
versions of Microsoft Edge, Google Chrome, Mozilla Firefox, and Apple
Safari (macOS).
Add-ins must work in all Office applications
specified in the Hosts element in the add-in manifest.
Add-ins must work across all platforms that support methods defined in the Requirements element in the add-in manifest,
For more information about the validation policies, please refers to https://learn.microsoft.com/en-us/legal/marketplace/certification-policies#1120-office-add-ins
We build an Outloook Addin and are testing it across different platforms.
It works on all the browsers (IE 11, Edge, Chrome and Safari), but not in the Outlook 2016 on Windows 10.
We root cause it, looks like the problem is Office JS API UI.displayDialogAsync() .
It does not open a dialog in Outlook 16 and the addin just hangs in there with the following progress message spinning forever,
[Your Addin] is working onr your [Request]
The closest thing we found on the Internet is this Stackflow post in which the answer says
the oldest Outlook build that supports this API is 16.0.6741.0000.
We are using 16.0.9226.2114, so we meet the requirement.
Here are versions of OS/Outlook and Office JS we use in the test:
OS: Window 10 Home, Version 10.0.16299, x64
Outlook: 16.0.9226.2114, 32bit (Version 1804)
Office JS: 1.1.5-release-next.1 (We download the exact package from GitHub and host it on our server)
Wonder is there any known issue of this API on Outlook 2016? Need some help here, thanks!
We have also been trying to debug Outlook 2016 using F12 developer tools .
But our addin cannot show up in the chooser page, no matter we launch the chooser before or after
we click on our addin. We have tried this on several windows 10 machines, but none of them work. Any suggestions that what we could possible miss here?
Seems to me that you had a similar issue to mine. For me adding the remote domain in the manifest resolved the case. Find and update the following section:
<AppDomains>
<AppDomain>https://your.domain.com/</AppDomain>
<AppDomain>https://auth.com/</AppDomain>
</AppDomains>
Proxy HTML works cause it's loading from your domain and still is viable solution.
It is possible to embed the 'Internet Explorer Web Browser' in an Excel Sheet using the Microsoft Web Browser Object. How does one Embed Google Chrome or Firefox in an Excel Sheet?
There is a project to provide a Mozilla ActiveX control matching the IE Web Browser Control Interface as much as possible. I am not following the progress but its supported version seems dated.
As for Chrome you could check out Chromium Embedded but it doesn't seem to support ActiveX so you would have to work something out using the .NET binding (CefSharp) in combination with VSTO and WinForms.
I have used CefSharp with WinForms application and it works quite well.
The samples are good for a quick start.
I have installed IE8 on my system. I usually test my application on this browser, but the problem arises when i got to know that the client is using IE7. Now how can i test my application on IE7?
One possible solution is to have dual booting on my system. So on version of Windows i can have IE7 and on another i can have IE8. But i really don't want to use this solution.
Another possible solution is to use PC Emulator [ Don't know what is this, just heard about these ]. Using which i can have multiple IE version simultaneously. Have you ever tried this solution? Please name any good FREE emulator.
Please let me know if there is any other better solution.
you can use
http://www.my-debugbar.com/wiki/IETester/HomePage
and here can you see all browser versions as picture
http://browsershots.org/
I got the solution. :)
In IE8, click on Tools > Developer Tools | or press F12
Then in developer Tools > select the browser mode [ available: IE7, IE8, IE8 with compatibility view ]
This is what i was expecting. :)
Microsoft provides a free set of Windows Virtual PC images for testing various versions of IE on various Windows service packs.
Virtual PC is also free.
Have you ever seen Microsoft Expression Web tool? It contains kick-ass tool for testing pages in various versions of IE - SuperPreview. And this tool also available free, you can download it here.
It's much more easy to use it instead of Virtual PC images. But it can't replace VPC completely because testing in clear environment is also very important.
This is a quick and easy web service solution, good for quick testing.
http://www.browserstack.com/
For those who are still looking for an answer here's a Chrome extension
It has over 6 millions users, and it claims:
Top 10 Chrome extension since 2009!
-- WINDOWS ONLY -- WINDOWS ONLY --
IE Tab exactly emulates IE by using the IE rendering engine directly
within Chrome. This will enable you to use ActiveX controls and test
your web pages with different versions of IE (IE6, IE7, IE8, or IE9).
-- FEATURES --
Create a list of URLs that will automatically open in IE Tab
Group Policy support for enterprise deployments
Securely use the old IE rendering engine
Edit Sharepoint documents instead of opening read-only
Use Java, Silverlight, and ActiveX in Chrome seamlessly
You can also look at Adobe BrowserLab:
http://browserlab.adobe.com
Microsoft has launched Modern.IE to help with this. Go here to download a test image for your preferred OS and visualization software.
http://www.modern.ie/en-us/virtualization-tools#downloads
How to fix this error in SharePoint:
"The list cannot be displayed in
Datasheet view. A datasheet component
compatible with Windows SharePoint
Services is not installed, your
browser does not support ActiveX
controls, or support for ActiveX
controls
It started to days ago, for apparently no reason. ActiveX is enabled on this site and I had everything working fine so far. Not sure what went wrong.
Thanks,
... from IE check out your Internet Options, and look under 'Programs'->'Manage Add-Ons'
When I had this problem it was because an add-on was missing or disabled... * thinks * "Microsoft Office List 12.0" or something.
I was getting the below in SharePoint 2010.
The Standard View of your list is being displayed because your browser
does not support running ActiveX controls.
Turns out the site (master page) was being rendered in IE9 mode and the datasheet supports only up to IE8.
The datasheet mode can be used temporarily by switching the Document mode and the User agent string both to IE 8, or permanently by using the meta tag X-UA-Compatible IE=8.
This is known issue and you have to install the hotfix provided by Microsoft.
The issue is addressed in the below specified link along with the URL for the hotfix.
http://www.himmeltech.com/blog/fix-for-datasheet-view-issue-error-in-sharepoint-2010/
Let me know whether the suggested solution fixes your issue
Please install below data connectivity component to resolve this issue.
http://www.microsoft.com/en-us/download/details.aspx?id=23734
This link helped me and it worked fine. Our environment was Windows 7 64bit and MS office 64bit as well, after installing this connectivity tools, user had a option edit the data sheet view in sharepoint.
I ran into the same issue after updating to Office 365 but remaining with IE 11 and Sharepoint 2010.
Issue:
using a 64-bit version of Office with a 32-bit version of IE
Reference: Technet
Resolution: Installed 2007 Office System Driver: Data
Connectivity Components
Seems like a client/browser problem.. do you have Microsoft Office installed? Did you change security settings in Internet Explorer?
My environment is SP2010 enterprise and after trying several solutions, I realized that the user that could not see the views in Datasheet style was because did not have installed "Microsoft Access" that is required when you are using views in datasheet style. So the solution for me was to upgrade that specific user from Office Standard to Office Professional
For me, I performed the following and it worked for me:
Open Control Panel and open Programs and Features
Find your instance of Microsoft Office and select it
Click change at the top
On the dialog that comes up, click Add or Remove Features and then continue
Make sure Microsoft Access Web Datasheet Component is installed under Office Tools/Microsoft SharePoint Foundation Support
Even if it is showing as installed, click Continue.
Let everything install, close any office programs out, then try again
These steps worked for me.