Recently I have encountered a strange error using HTML 5 video player and SharePoint 2013. Customers wanted to embed a few video files with subtitles to their portal. They used mp4 videos and WebVVT subtitles. The problem was that they didn't see subtitles in IE.

Html5 Video element is used to embed video content in a document. The video element contains one or more video sources. To specify a video source, use either the src attribute or the <source> element; the browser will choose the most suitable one.

WebVTT is a format for displaying timed text tracks (e.g. subtitles or captions) with the <track> element. The primary purpose of WebVTT files is to add text overlays to a <video>. WebVTT is a text based format, which must be encoded in UTF-8 format. Where you can use spaces you can also use tabs. More information about WebVTT can be found here.


Recently I have found a nice library that made my life easier. According to authors it is the most comprehensive, enterprise-ready framework for provisioning SharePoint artifacts on SharePoint 2010, 2013 and O365. SPMeta2 is a code-first provision library supporting the provision of more than 120 artifacts in robust, highly repeatable and testable way while leveraging either one of the CSOM or SSOM SharePoint runtimes.

The library has the github repo with a documentation and lots of examples. The library is distributed via NuGet

Authors claim that SPMeta2 fully replaces XML allowing you to focus on writing clean, unified, reliable and reusable code.

I have tried to deploy a few lists and almost everything have been handled by SPMeta2.


Nintex Workflows is an awesome highly customizable product, that makes life of many people easier. But sometimes you need to write a few lines of code to integrate your forms with nintext workflows. There are few articles regarding this topic, but most of them use web service or some of the nintex dlls.


Recently I have worked on a small SharePoint onprem project and a customer wanted a custom List View/Edit forms for one of the lists. Long story short - they wanted a custom control to manage attachments.