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
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?
After importing / restoring a site collection from a different environment, you might have the need to terminate all of the running workflows. For instance, to stop them from e-mailing people or firing off other events which should not be fired from within your local dev environment. Whatever reason you might have, here is a
I rarely discuss the things we do at Atos here. This time I’m going to make an exception, to tell you about a pretty neat hosting service we offer to our customers. So yes, you might regard this post as an advertorial and yes; you may contact me for more information. If that’s not your
In my previous blog post I wrote about host named site collections in SharePoint 2013. As this is the recommended way to go according to Microsoft, you should definitely consider it for new SharePoint deployments. But with these URL’s bound to your site collections, you can get into trouble quickly. It’s important to get a
With SharePoint 2013, Microsoft claims we need to rethink our architecture. Host named site collections are the way to go, and preferably all within the same web application. But what are host named site collections and what do we need to take into account when setting this up? Update. Check out part 2, detailing how to
Those of you who know SharePoint, probably also know those annoying problems you just cannot get your head around. Well today I had one of those problems.
There is a lot of information on how to link SharePoint 2010 or 2013 to an AD FS instance. But for some reason, most of those blogs include a manual step to enable the newly created authentication provider in Central Admin. I don’t like manual steps, so here is a little script which does the same,
I have finally come around to messing around with apps in SharePoint 2013 again. Way too late, I know, but better now than never right? So when I was building this provider hosted app, I wanted to make use of the JSOM libraries. When you check out some of the solutions, you will find code