It seems this issue arises in almost every migration project: “Hey, we have a bunch of HTML based files which we’ve uploaded to SharePoint, but now they don’t work any more!”. With “don’t work”, usually it means the user is prompted to download the file instead of being able to just view it in the browser. So
Month: October 2014
When you’re writing provider hosted app, you probably know the procedure for publishing those. That procedure includes packaging the app package, which is an action Visual Studio will do for you. You enter your website URL, a client ID and you’re off. But what if you host your app on multiple locations having different URL’s?