The time has come. Another release for NMoneys is out the door! Go and get the binaries.

What can we expect from this

  • Complete XML documentation. Use the supplied NMoneys.XML file to get get intellisense for all methods.
  • .TryParse() and .TryGet() methods are really and truly .TryXX() and do not throw exceptions anymore.
  • USN and USS currencies have been added, as a happy side-effect of the completion of a tool to scrape information from the ISO website.
  • A simple but effective build script has been added and with it new deployment possibilities

Not a lot? More to come.

How to “install” NMoneys

0s and 1s

Downloading the binaries, extracting them to the folder you keep your external assemblies and adding a reference in your project is still easy enough.

From the sources

If you are a developer, and want to build the trunkmaster, you might be interested in knowing that the developer’s quick start guide has changed. We still require you to use MSBuild, but using the NMoneys.build file will:

  1. compile the binaries
  2. run the whole suit of unit tests
  3. generate test reports
  4. create a NuGet package
  5. copy binaries, documentation and NuGet package to the output directory (%trunk_working_folder%\build)

Then, get the artifacts you need from the output directory while they are fresh and (ab-)use them happily.

No package?

Well, if you had read the previous point, you would have noticed that I mentioned NuGet. In case you did not know, NuGet is a package management system for the .NET platform intent on simplifying the process of incorporating third party libraries into a .NET application during development.

If you are thinking “yeah, cut it… How do I use it?” you are in the right mood. You can deploy NMoneys using the NuGet package management. Download the package NMoneys., host it in your favorite corporate/private repository and let your developers feel the joy of package management.

Why is it not part of the official feed? Well, NuGet is very young, active and volatile. Besides, getting a package in the feed is a royal pain in the neck. As a side note, I was not able to accomplish it; not a mercurial genius myself, but I was not even able to clone my fork. That is why, until it matures enough and makes it easier for lazy package developers as myself, it is not going to be included in the feed.

No precious stones?

Nu users are also welcome. For them, I created a gem. It was surprisingly easy to generate and submit to the ruby gems repository, even with my limited ruby knowledge.

Sorry, fellow developers, but I did not automate the gem generation as I was not willing to impose a dependency on ruby for people building the sources. But you can get it from rubygems.org, they have the infrastructure already in place.


Go, spread the word, download it and have a saying.