SPSync 0.9.8

Ok, here we go. The sync engine got a major refactoring. It is now a lot faster to get the changes from SharePoint and to iterate over the local files. That means it is now just a matter of seconds to “analyze” the changes even for more than 1000 files and 1 GB. It should therefore also be able to sync your libraries with thousands of files in a reasonable time.

The other big news is the complete new setup experience. Just click here to download and execute the setup. It takes just a few seconds and SPSync should start. That’s it. No “Next”, “Next”, “Finish”, nearly no time and no local admin rights required. Even better: Updates gets automatically installed in the background and on next restart of the app you are up-to-date.

Please report all bugs to support@spsync.net

SPSync 0.9.7 including CLI

SPSync is approaching version 1.0. Today I’m happy to announce that SPSync now works more stable and also includes a new command-line interface.

It should work now with all SharePoint 2013 on-prem and Office 365 sites without any issues during connecting or displaying the “select folder” dialog. As the “SharePoint Url” you can now use more formats and SPSync will try to figure out the site, the library and the authentication method automatically. For example, these formats are all fine:

The most requested new feature is the command-line interface. You can find SPSyncCli.exe in the install folder.
It accepts two parameters. The local folder and a “preview” mode parameter.

You have to configure a sync connection like before with the GUI. After that, you can sync a folder with the following command:

SPSyncCli.exe “C:\Your\Sync\Folder”

If you just want to see, which files will be modified (but don’t want to do it now) you can sync in a “what if” or “preview” mode:

SPSyncCli.exe “C:\Your\Sync\Folder” true

The result looks like this:


SPSync now uses a different location for the metadata. It is now directly within the local folder under “.spsync”. Therefore you might get a conflict message the first time you sync with the new version.

Download the new version here: http://spsync.net

SPSync - The OneDrive for Business alternative

I know, the last update is almost a year old… But yes, I’m trying to work on it when I find some free time. So this update brings some important changes.

What’s new?

First of all, to add a new sync configuration, the dialog has only a few fields left. SPSync will try to find every other setting automatically for you. Here is the new dialog:


As you can see, the advanced configuration dialog can be opened via the link. The automatic detection will only work if you are using NTLM/Basic (On-Premises) authentication or Office 365. For ADFS you need to enter some more info on the advanced dialog.

Another new feature is that you can now configure, whether you want to sync in both directions or only one of them (Local->Remote or Remote->Local) which was a suggestion on UserVoice with a high vote. Also deleted files (local or remote) are now always send to the recycle bin and never get automatically deleted for ever.

With this new version I’ve decided to drop the support for SharePoint 2010 (and before), because of some missing features for the upload/download handling. This is to make the development much easier and better to maintain. That’s also why SPSync requires now .NET 4.5.1.

Last but not least, a lot of bugs are now hopefully fixed. If you find something, please send me an error report and attach the DebugLog.txt from C:\Users\%username%\AppData\Local\SPSync

Download the new version 0.9.5 here: http://spsync.net and leave a comment or drop me a line at: support (at) spsync(dot) net

PS: The next new feature will be to be able to sync sub-folders within a document library as it has already 20 votes on UserVoice.

New Microsoft certifications

As I’ve mentioned here, Microsoft recently had a promotion to get up to 5 free vouchers for some specific exams for Prometric because after 31th of December, Pearson Vue will be the only exam provider.
I decided to try three of them:

I’ve passed all of them, which is especially great for the Azure exam, because that one was really hard.
With the two Office 365 exams I’m now a ”Microsoft Certified Solutions Associate for Office 365” (MCSA: Office 365).

You can find the details how to access my transcript here.

SharePoint 2013: Timeout on ClientContext.ExecuteQuery

Ok, this one is a strange issue.

I have created a console app with Visual Studio 2013. Added the “App for SharePoint Web Toolkit“ NuGet package to get the SharePoint.Client.dll
Then wrote just a few lines to test if it works:

        static void Main(string[] args)
            ClientContext context = new ClientContext("https://sharepoint/sites/test1");
            var web = context.Web;
            Console.WriteLine("Title: " + web.Title);

This is against an on premises installation with Kerberos authentication (NTLM and Basic are also enabled). On the line context.ExeucteQuery(); it just waits a long time and then gives me a timeout and 400 error.

The weird thing: If Fiddler is open during the execution, everything works as expected. No timeout, no error.


The solution is fairly simple:

Just attach a handler to the ExecutingWebRequest event and set the WebRequest.PreAuthenticate to true:

        static void Main(string[] args)
            ClientContext context = new ClientContext("https://sharepoint/sites/test1");
            **context.ExecutingWebRequest += context_ExecutingWebRequest;**
            var web = context.Web;
            Console.WriteLine("Title: " + web.Title);

        static void context_ExecutingWebRequest(object sender, WebRequestEventArgs e)
            **e.WebRequestExecutor.WebRequest.PreAuthenticate = true;**

BlogEngine.NET update

Mein Blog ist nun ein wenig renoviert und auf dem aktuellen Stand (BlogEngine.NET 3.0).

Dabei habe ich auch Kategorien zusammengefasst, gelöscht und vieles andere gerade gezogen. Außerdem verwende ich nun ein neues Theme. Wenn euch was auffällt, einfach einen Kommentar hinterlassen.

Visual Studio Extension: SPDeployer

With SharePoint 2013 you can create great solutions not only with a "SharePoint Hosted-App", but with a plain JavaScript file within a Content Editor Web Part. Vesa Juvonen named it app script part pattern.

So development today is like:

  • Open the style library in Explorer and open the javascript file with your favorite editor. Not ideal, because you are not working within a solution in Visual Studio, so no source control integration, etc.
  • Use SharePoint Designer to work with the files –> Not a development environment you want to work with


Here comes my Visual Studio extension to the rescue. Install it directly from within Visual Studio->Tools->Extensions and Update. Search for SPDeployer or download directly from the Visual Studio gallery.

Open a solution with your web project, then click Tools->"Add SPDeployer to project". This will add a new spdeployer.config file to the currently selected project.


Just enter the details to you SharePoint dev site and add a line for each file you want to have SPDeployer automatically upload on save.

Now whenever you make changes in one of the monitored files, it will automatically upload to your SharePoint library.

You can find the sources on GitHub. Feel free to add issues or pull requests.