NUtility Class Library 

Contributing

With the progression of NUtility relying on the time of contributors, there is always more work to be done. Whether you're a programmer, a writer or just someone with some spare time, there's always new functionality which needs researching and implementing, unit tests which need programming and documentation that needs writing.

In developing NUtility we try and adhere to a set of development best practices to ensure NUtility achieves the quality required of a reasonable class library, which means before code is released it msut be unit tested using the NUnit testing framework, and documented using the NDoc documentation tool. Finally, to ensure all releases are consistent, we perform all software builds using the NAnt build tool.

If you're interested in working on NUtility then please contact mark.easton@blinksoftware.co.uk with a brief description of your skills, experience and which areas you'd like to work on.

Contributors

• Brian Ritchie - Wrote the Mono.Data assembly from which the ProviderConfigurationHandler was plagiarised.
• Rafael Teixeira - Wrote the Mono.GetOptions assembly which was scavenged for the response file functionality.
• Rick Parsons - Provided a detailed description of the Soundex algorithm, which fixed an old bug in the Soundex implementation.
• Mark Easton - Wrote the COM components that the original Blink.Utillity was based-on, and most of the current NUtility code and documentation.