It should be no secret that I have been very absent from both my OSS libraries and my writing.
Maybe that will get better, maybe not. But one thing is for sure: the .NET scene has moved and I have not moved along with it. Time to slowly amend that.
It is not a coincidence that there is a new release of NMoneys around the New Year.
Countries usually take advantage of this hard change to perform drastic changes in their monetary systems and so it is up to NMoneys to catch up with reality.
This year, however, there is so much more...
After migrating NMoneys (and NMoneys.Exchange) to support .NET Core it is time to lend a little love to the support for serialization via third-party serialization libraries.
This support operates in a very different way than the usual: 1. install package 2. some library is referenced 3. time to code against that library as it comes in the shape of source code that are added to your solution and compiled as part of it.
I have already gone through some of the choices I considered when porting my Open Source Libraries to support the .NET Core platform.
Let's dive into details of each of them, as each has its own peculiarities.
This is a honest question for which, fortunately, there is an answer now.
I am sure that there was one before, but sure as well that NMoneys could not provide an answer easily.
Until now.
Under this very weird title comes an important piece of news: the company I work for (proxying through me -or the other way around-) has released new Open Source Library: Vertica.Utilities.
And it is worth checking.
I recently went about the task of migrating most of my OSS libraries to the "new" .NET Core platform.
I would like to share with others some of the choices I made and the motivations I had. Besides, I also want to reflect about the pains and gains of doing so.
Behind this, somewhat, catchy title lies a new version (4.1) of Testing.Commons.NUnit and no golden rule about how to discard potential dates in the digital era (would be rubbish advice anyway).
It is not a major version, but I believe it is an important one since there is a little history behind it.
Because there is little justification besides learning to spend the time upgrading SharpRomans to .NET core.
But learning is fun and quite enough for me.
People had been asking for it and now it has finally come: .NET Core support for NMoneys and Testing.Commons.
After some disappointing trials with beta tooling and after the release of Visual Studio 2017 I have been able to provide support for those of you that are way ahead of the curve and need currencies and help with tests.
I will never stop being amazed by the wonders of OSS.
This time, the turn is for Testing.Commons to find a new home and, again, as with NMoneys, such home will be GitHub.
In a previous rant post I complained stated my discontent with Microsoft’s Live Account recovery system but it all stemmed from the fact that I did not own a laptop other that the one I use for work.
MongoDB is a public favorite of mine. It was the first document database I worked with and despite their quirks (less and less as time passes) I can strongly recommend to have a look to it when you are searching for a server-based, solid document database.
JSON has become one of the most widely accepted data interchange/representation formats. Not only as a Web data interchange, but also as data representation of multiple document databases.
One would not believe it given the weather here in Denmark, but it is summer and what happens with summer? Amongst other interesting things here comes an update of some OSS projects.
…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.
I confess. It was a bit backwards writing about how to handle indexes in development involving multiple databases without writing about handling multiple databases. It’s never too late.