We are developing a Mail via App for Office " Hosted in office 2013 Client" I can develop the app and deploy it against my localhost for testing and developing... How do I go about creating different environment for this app... i.e. staging environment so I can deploy in an environment different than production.
What different environment are you talking about?
Office Apps are supported by Office 2013 only. You can open a web browser and open the OWA to see how your App works there.
Related
I developed and On Send Add-in for outlook, it works fine when I host the service locally and add it as the custom add-in.
Now I need to deploy it on our organisation's office 365, and I have to host the service somewhere (written in nodejs).
my question is
1. is there an out of box solution from office 365 to host the add-in service?
2. if I have to host it on a server within our organisation, I guess I have to update the manifest.xml to use the new servers' IP instead of localhost. Will office 365 be able to access the IP?
Thanks
You deploy it just as you would any other kind of web site, as that's what an Office add-in basically is. There is no special Office 365 way of hosting a web site that happens to be an add-in. But you would have to update any URLs in the manifest to point to your production site. You still need to deploy the manifest itself to the end users, or to an admin who can install the add-in for all users in their Office 365 tenant.
I am trying to setup a Dynamics CRM 2016 Internet Facing Deployment. The application/SQL server is a Windows Server 2012 machine and CRM is hosted as a separate website(not the default website). Where do I install AD FS? Is it supposed to be on the Active Directory server or on the application server? Are there any other factors to be considered?
yes you can deploy your ADFS on the application server. If you look at page 10 of this deployment guide - https://www.microsoft.com/en-us/download/details.aspx?id=41701 you can see that same server deployments are supported. Although, it's a bit messy and separate server deployment is recommended.
One thing to keep in mind is that whenever you need to restart your application server (installing rollups\updates) your ADFS will go down as well, and if there are other applications using it, your users will loose access to them.
It could be any server but I would suggest to use separated server for that purpose.
I have SharePoint Foundation 2013 installed on a server. I want to do the development using My machine. I have Visual Studio 2015 installed, with Office tools. I can create an app and deploy it to office 365. But when i try to deploy to an on-premise server I get the following error;
Error occurred in deployment step 'Install SharePoint Add-in': The HTTP request was forbidden with client authentication scheme 'Anonymous'.
Please refer this the below link. As per my understanding Office 365 uses https and local used http. sslshopper.com/iis7-redirect-http-to-https.html. Also have you created a dns entry in your local server (host file) please check.
Can you use a Provider-hosted apps and an Autohosted apps for Office 365? How? You write server side code in them, so how can they work with Online?
You can use provider hosted apps and autohosted apps with SharePoint Online. They work because your server side code is not hosted on SharePoint - in case of Autohosted apps your code is hosted on Azure web site, in case of provider hosted some provider hosts it. So basically in your SharePoint site you have "link" wrapped in app package which points to external web site. External web site can use some features of SharePoint (for example get its data or use chrome control).
Does anyone have a detailed write up on integrating Team Foundation Server 2012 (on premise) with SharePoint 2013 (on premise), specifically where SP is setup with separate Web and App Servers.
My understanding is that the TFS extensions need to be setup on the Web and App Server but installation on the Web Server is failing.
When configuring the SP web app on the TFS Server, do we point it to the Web Server or App Server?