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.
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.
This time, the turn is for Testing.Commons to find a new home and, again, as with NMoneys, such home will be GitHub.
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.
That is an enigmatic title to write about serialization. Well, sort of, as one of the meanings of the word refers to that concept.
But writing about successions is not my intention. My intention is to write about the technique that allows objects to be persisted to another medium different from their native memory space and more specifically on how to test serialization of objects.
Let’s throw a party!
Configuration in enterprise application is a fact of life.
My take on it is as follows: delay it as late as possible and hard-code in anger until someone asks for a change. Then, accepting the fact that is likely to happen again, the value is pushed into configuration.
GUIDs are precious little things. Useful, annoying at times, but lovable nonetheless. Cherish them as if they were unique (all pun intended) and they will pay your love back.
While developing the improvements for the Generate class of Testing.Commons I faced an API design challenge that I, at least, consider challenging.
Face it: time is everywhere and cannot run away from it. That is why I chose time to be the subject of the first release of Testing.Commons, a mere 0.1.
Classes that deal with time in the BCL (DateTime, DateTimeOffset, TimeSpan) might have their issues. They might not be accurate. They might not be correct at all. There might be some better alternatives. But they are not going anywhere, anytime soon.
As the reader might have notice, I am a big advocate of testing. During the years that I have been practicing some flavor of testing I have been developing, borrowing and using small little classes (or bigger ones) and techniques to make my life easier and my code suck a little less.