Why 2.5?
Previous to 2.5 came 2.2. But to highlight that changes between the two versions are pretty “dramatic” I chose to bump the version number. Fear not, not everything has been turned upside down.
NMoneys. Bumped to 2.5
Svar
Tag-arkiv: Frameworks
NMoneys 2.2
It is hard to believe the last release was on September. That only means one thing: I was about time!
There are quite a few changes in the release, so I will get straight to the point(s)
Money Allocation
2.2 should be a happy release. Why? Well, besides the fact it is the first release in more than 6 months it is the first one that contains code contributed by someone else but me.
Thank you, Berryl, for the feature, let’s hope it’s useful to many.
One After the Other
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.
Testing with ExpectedObjects
The other day I read an interesting post about testing and a library that might help in some cases, its title is “Introducing the Expected Objects” library. I thought it might be useful and so I spent a spare evening writing some code to check whether is something that could be useful for my team.
The Problem
Imagine you are testing a complex object: multiple properties, graphs of objects, collections… and you want to test the outcome of some operation on it and you are using NUnit as your testing framework.
Which strategies are available?
Testing.Commons goes 1.0
Let’s throw a party!
A Big Gap
Wait a second? Last release was 0.4.0.0, when stuff to test the profile system was added. “Either you have been terribly busy or you are tricking us.”
Well, more of the latter if you check the amount of code of the deltas committed. In reality my plan was to go 1.0 when all the code I previously had was ported. It turned out to be less than I thought as I trimmed out some parts I cannot use and clipped redundancies.
NMoneys.Exchange gets an Article as well
I am sure you are aware of both NMoneys and its companion.
I have written another article in The Code Project showing what can this extension to NMoneyscan do for you.
Enjoy your reading and comment on it.
Daniel Gonzalez Garcia
Vertica A/S
NMoneys 2.1.0.0
Not a lot of movement in NMoneys until now.
But the unthinkable, has happened: I have received an email notification for a change in the ISO standard for currencies!! After more than two years subscribed I finally received my first amendment newsletter. I totally attribute this event to changes in the maintenance agency, which changes are very welcome, Excel and XML tables of current and historic currencies, amongst others.
NMoneys goes 2.0 and Gets Company
Wow, after a 1.6 version I decided to jump straight to 2.0.
Is it that big of a change? Well, not really, maybe a couple of breaking changes and features. But NMoneys 2.0 is just a side dish, the entrée is… NMoneys.Exchange 1.0
Is NMoneys Already Dead?
Not a chance! NMoneys.Exchange might steal some of its older brother’s thunder for some time, but NMoneys still plays the star role.
Nmoneys Gets an Article
Ahoy everyone.
I have published an article in The Code Project showing off some of the things NMoneys can do for your application.
Have a read, discuss and get involved. It is worth it, if you ask me 
.
Daniel Gonzalez Garcia 
Vertica A/S
Nmoney 1.4.0.0
After the previous service release, here comes a new one. It is not a ground-breaking release (I suspect we won’t be getting many around here) in terms of features but it was fun to create it.
The Default Non-Zero Enumeration Re-Visited
One of the motivations of the 1.3.1.0 release was address a problem in which default instances of Money had an undefined enumeration value. I kind of solved, but thinking about it later on I found a more convenient and performing way of solving the problem: using good old nullables and the not less venerable Nullable<T>.GetValueOrDefault(default).
