I had to rebuild my Mac and installed Office for Mac 2016 (from an Office 365 subscription). I am not able to click on a link on a web page and edit the document with WebDAV (iTHit implementation not SharePoint). I was using Office for Mac 2011 before the rebuild and that was working...When I clicked on the link using Safari, the pop up for allowing the SharePoint browser plug-in did not display. Since the site I am connecting to uses basic authentication over a non-SSL connection, I used Terminal and ran the following command: defaults -currentHost write com.microsoft.registrationDB hkey_current_user\hkey_local_machine\software\microsoft\office\15.0\common\internet\basicauthlevel -int 2
I was not able to have the document open with Word.
I uninstalled Office for Mac 2016 and deleted and file that reference Microsoft..Then I installed Office for Mac 2011 and ran the command above with \14.0\ instead of \15.0\. I can edit documents with WebDAV.
What settings will allow the use of Office for Mac 2016?
I am having a similar problem and trying to open / edit office documents from the browser via WebDAV / Sharepoint plugin. This used to work with prior office versions, but not with Office 2016.
Apparently Microsoft dropped the WebDAV support for Office 2016 which would also affect the itHit library: http://answers.microsoft.com/en-us/mac/forum/macoffice2016-macword/using-office-for-mac-2016-to-edit-a-document-from/2aee8656-313a-4c97-8223-9a20373b9891
We have retested IT Hit WebDAV Ajax Library and Ajax File Browser with Office for Mac 2016.
Opening and saving MS Office documents from a web page works just fine. The Word, Excel and PowerPoint documents opened from server successfully, edited and saved back directly to server with no problem.
For testing we were using MS Office for Mac Version 15.22 (160506) with default install options and ajaxbrowser.com running Ajax File Browser v3.0.0.2465 (WebDAV Ajax Library v2.0.1735) as a testing server. The MS Office was installed on a clean Mac v10.11.3 that did not have MS Office 2011 installed previously, so there is no any remains of protocols installed by MS Office 2011. There is also no IT Hit Edit Document Opener installed on this machine.
The confusion around WebDAV being not supported is probably caused by a new MS Office "Save As..." dialog that shows the WebDAV location from which the document is opened but it does not allow browsing WebDAV folders. Even though, saving under new name in the same folder works well in "Save As" dialog.
Related
I have an Add-in I have written for Microsoft Outlook. The Add-in runs in a task pane. I have a button on the html in the page that opens a new window using Office.context.ui.displayDialogAsync. This button works fine in the web client, but when clicked in the full Outlook client, a window appears and disappears in a split second. This Add-in was developed outside VS so not sure how I can debug apart from in web client, which not does have the issue.
The domain is the same, and the domain is in the appDomain of the XML manifest. The URL is also https.
Does anyone have any ideas, have I missed something that says this isn't available in full client and only available in web client?
About Outlook version:
Version 2102 (Build 13801.21004 Click-to-Run)
Microsoft Office for Outlook 365 MSO (16.0.13801.21002) 64-bit
If I clock Office Updates, it tells me Office is up to date.
Update
I have another machine with Outlook installed, and I have discovered the dialog opens fine on the full outlook client. Looking at the version for that version of outlook (logged in to the same Office 365 account), the version shows as:
Version 2110 (Build 14527.20226 Click-to Run)
Microsoft Office for Outlook 365 MSO (Version 2110 Build 16.0.14527.20168) 64-bit
So it looks like maybe the earlier build had an issue in Outlook?
Would you like to share a screen recording in the machine where the API is not working?
Besides, you could also try a test add-in with this: Manifest.
It's an app command so you can click "Show Taskpane" first, and then click "launchDialogSameOrigin" button in the taskpane. You can observe whether the dialog is working correctly in this add-in.
Thanks.
We have an add-in that works fine on Outlook for mac but not on windows for IMAP (Gmail) accounts.
Is the setup different to how the IMAP is configured on MAC and Windows?
Mac Version - 16.41 (20091302)
Win Version - 16.0.13127.20402
This is an issue because a lot of our users are unable to use the add-in when they have multiple accounts in Outlook on windows (of which most are IMAP - Gmail)
I would have thought it would be other way around where Add-ins would be available on Windows and not on Mac since a lot other things are not supported on Mac within outlook.
Are there settings that can be changed to make them available on windows or of anyone knows about this being available in the future?
----------------- UPDATE --------------------
Mac Version - 16.42 (20101102)
So, this morning 19th Oct, 2020. I got an Outlook Update for mac and as per the screenshot below, you can clearly see that I am using a Google Account (IMAP) and the add-ins are availanle.
Outlook Web Add-Ins are only supported on Outlook accounts connected to an Exchange server. Further documentation here : https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/add-in-requirements
I am having a horrible time getting started at creating an add-in for Outlook. I want to use the new html/javascript/manifest approach. I have been able to create a manifest and application which works great with outlook.live.com. Where I am completely getting stuck is with desktop Outlook. How do I install/debug my add-in with desktop Outlook?
I cannot find anything in the UI which will let me add this style of add-in. Additionally the Microsoft documentation did not make things any clearer. Their docs seem to hint using this type of add-in is only possible if you are connecting to an Exchange server.
Any help would be greatly appreciated.
Yes the add-in will load on Outlook desktop only if your mailbox is Exchange. I am not sure the add-ins work with a personal Microsoft account (e.g hotmail.com, outlook.com) and Office desktop. Keep in mind that the support of mail add-ins for personal account is relatively new (officially announced in march 2016).
To develop your add-in I suggest you to use a organizational account (i.e. Office365 account). Support for organizational account has been released in 2013 and is a much more mature solution for you to get started. You can have a free dev account at dev.office.com.
Edit: October 2016 personal account are supported now by "Personal mailbox accounts" aka outlook.com accounts
Let us keep in mind that a mail add-in is not installed on a mail client (desktop, OWA) but on the mail account. When you "install" an add-in you only set a xml file on your mailbox that basically says "there is a web add-in out there called X and that is served at this url...". Then, if you install add-in X on your mailbox smaclell#mytestcompany.onmicrosoft.com, this add-in will load the add-in web iframes whether you are consulting your mailbox with Outlook Web Access (OWA) or Outlook Desktop.
To install the add-in for one user mailaccount, you have to use the Outlook Web Access. See this blog post. Note also that you can install the add-in for the whole organisation (Admin > Exchange Admin > Add-ins). Finally, Visual Studio is also able to push the manifest to your office 365 mailbox. To have this you need Office Development Tools.
For debugging in Outlook Desktop, I know two approaches.
Use the Office Developement Tools with visual studio
and select your sample add-in project as 'Starting project' and in properties select 'Office Desktop'.
Plain web development.
Personally, I do not use really much the Office Development Tools. I install manually my add-in with "https://localhost:XXXX" for url and I start the web project on IIS express to do the debugging. For stepping into the source code, I use the debugger of my browser (Chrome, Edge, IE etc.) when browsing in OWA. When I need to step into source code specifically on Desktop (For windows or for Mac) I use Vorlon.js see also this blog post.
My advice is also to test/debug frequently with IE 11 (still available in Win10!) and OWA. Indeed, the browser used internally by Office Desktop for the add-ins is IE.
I am willing to develop an Outlook add-in for both, the web and the desktop version. My questions are:
When I upload a new version of the add-in, is it automatically updated (per default) in the users' devices / outlook web accounts?
Is it the same add-in for both, web and desktop, uploaded to office store?
If you are only updating the source code of the add-in (HTML, JavaScript, CSS) on the web server where you host it, then all users will get that right away since like Dmitry explained, Outlook will download the page like a browser would download it. So you should be careful updating the page of the production add-in - users will get the updates right away (although keep in mind that user's system/browser may cache previous version of the page for some time), so if you break the page or functionality of the add-in, users will get affected immediately, which may result in negative reviews for your add-in in the Office Store.
If you are updating the manifest XML file of the addin, then you need to publish new version of it to Office Store. Once it's published, that new version will automatically be updated for users who already installed an earlier version of the add-in. This automatic update will happen after they login to any of their Outlook clients that support add-ins.
Yes it is the same add-in for both web and desktop - that's the beauty of the new Office add-ins!
Hope this helps.
Web addins are never even stored locally, (desktop) Outlook downloads the addin source code every time it starts up.
Our company recently switched to Lync 2013 and I noticed that under "Settings/My Profile Picture" there is no longer an option to specify a profile image. In Lync 2013 you could at least set a picture with less than 30kb that is hosted on a webserver.
The funny thing is I can use my Lync 2013 server account with the old Lync 2010 client and then I'm still able to set a profile picture (tested & woks).
Seems as Microsoft just killed this feature in the client but not on the server (LOL!?!?).
I would like to write a tool to be able to set a picture without having to install the old Lync 2010 client. Any hints, solutions or something to read?
Update as of 12/11/2013
The latest Lync update (Lync Client CU3 (November Update)) has the option to set a photo added back to the GUI.
Link to the KB Article
Link to the Download
Article with explanations and screenshots can be found here: Lync Client CU3 (November Update) – Show a picture from a website!.
Original Answer
This question comes up more often. It's indeed just a user interface change between the Lync 2010 and 2013 clients, the option to set an image URL has been removed. Underwater this option is still available though, and you can publish a Photo URL to the server from a user endpoint, or from a powershell admin screen as posted in GodEater's answer.
I answered with a description on how to publish photos using a user endpoint (wheter from client SDK or UCMA) here: Display User Picture in Lync 2013
Someone's implemented this as a powershell script here (and I've tested that it works on our Lync 2013 infrastructure) :
http://gallery.technet.microsoft.com/office/Add-Personal-URL-Photo-in-df0136ea