To translate this to code, we need to check if the querystring parameter et is present in the URL, if it is, we know that the app is opened in the browser. Note: I found the difference when looking at the requests in Fiddler. The URL loaded in the rich client context looks like this: Many end-users use Outlook it is the standard for many companies. The same will happen if the backend server goes down and Outlook cannot reconnect. The URL loaded in the OWA context looks like this: If you have a drop in connectivity, Outlook will show it is disconnected and flash errors. If the app is opened in a rich client context, the querystring parameter will not be present. That querystring parameter is only present if the app is opened in the Outlook Web App context. The first solution is to check the URL to see if it contains a querystring parameter named et. Solution 1: check the querystring parameters Eventually it turned out that you have two ways to check in which context your app is running and they are really simple to implement. By default you have the option to set the startpage for the desktop, tablet or mobile view ( Set up a mail app for Outlook on tablets and mobile devices), but you do not have the option to change the view when opened in a rich client. During the development for my proof of concept mail app, I needed to know in which context my app was running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |