nMoneys Moves Forward…
…by looking into the past.
Because that is what it should be considered when it stops supporting a version that is 7 years, 5 months and 2 days old; for one that is 5 years and 9 days.
Those are the the age difference between the previous .NET 3.5 and the currently supported .NET 4.0 according to WikiPedia. So I guess that very few people will complain about the minimum requirements imposed over this new version of NMoneys.
Well, someone complained about a concurrency problem and even though I have never, ever experienced such a race condition, fixing an issue always feels right.
I could have done differently. I could have back-ported just
ConcurrentDictionary, or use someone else’s back-port; but, while at it, I suffered from the “falling into the rabbit-hole” syndrome and foolishly holding onto the ancient version felt like the wrong-thing-to-doTM.
And so I decided that 188.8.131.52 will be the last net35 compatible release.
Home, Sweet (and New) Home
Nuget packages will continue being the preferred and main deployment method, but binaries will continue being offered.
Since the de-facto closure of Google Code’s download service, binaries had been provided by Bintray. Well. it’s not that thy do not offer a good service, but given the whooping grand total of 4 binary downloads I think I can go with the simpler, more integrated and less-featured GitHub Releases.
As a result, binaries will be available in the Releases area of the project home from now on.
Moving away from a dying code repository opens up a world of possibilities. Amongst which is Continuous Integration using Appveyor.
Right now it is an out-of-the-box build (compile + run tests) but I will be investigating further automation in the near future.
Oh, and the badge is nice
And a Small Change
A colleague of mine pointed out the fact that the good people of Sweden changed the way they prefer writing big numeric quantities, as pointed out in this Wiki page (in Swedish). And so, I obliged.
From now on, the default way a big monetary quantity in
SEK is not using . as a group separator. But, of course that default behavior can be overriden:
1s and 0s