Basically, the .NET calendar code does not support transitions between the Gregorian calendar and the Julian calendar ... and even if that were the case, I would not expect it to support the oddities of the Swedish situation, do one of them. Keep in mind that even in βnormalβ cases, switching occurred at different times in different cultures. There are many other oddities around historical calendars, too - see the Noda Time page for some examples. I especially love the British calendar doing strange things in 1735.
Cutting tools are very difficult to simulate, as you end up with gaps that make all kinds of code just explode. You will either end up with an incredibly bulky API that will work for everything, but it is difficult to use in all cases, or a simpler API that works on 99.999% of the software requirements, but does not handle historical corner cases. Some APIs (such as Joda Time ) model thinning in a way that is simple enough, but ends up with some APIs behaving strangely.
For Noda Time, I decided not to try to model it at all - if you are in a situation where you like dates until the 19th century, you will probably be in such a specialist situation that in any case you will introduce a lot of your own things.
source share