$ 0 0 I met this problem at past, I solved it by using the Nuget Management to specify TimeSpan2 2.1.3 instead of 2.1.4 (VS2015 has this feature). Hope this helpful.