We have previously announced about the price changes to Smarties 2008 from 1st of August. After the re-evaluation and seeking professional advice we will make significant changes to the licensing model that also reflect further changes to Smarties 2008 pricing.

In this release you would find five new commands, few enhancements, and four fixes. The main focus of this release was the sorting features in .Net. Now you can create sortable collections and implement IComparable and/or generic IComparable interfaces effortlessly. These commands are part of creating rich classes using Smarties 2008.

From 1st of August the Single Developer License will cost $60 and the number of installation will remain unchanged. The Corporate License pricing will remain unchanged but the number of installations will be reduced to ten machines.

MojabSoftware does not charge for major/minor upgrades therefore we would increase the license fees according to the value of Smarties 2008. The development is still very much on going therefore we would increase the value of your investment in Smarties 2008.

Storing a collection of reference types and value types is a common practice in Software Development. Since the introduction of the Generic Types in Framework 2.0 working with collection elements has become much easier.

The ArrayList type used to be the common type for storing objects but the new kid on the block “Generic List” has taken away the popularity from the ArrayList. Since elements were stored as an object casting reference types from object to enclosing type needed the extra coding and decreased the performance. With value types the developers faced the boxing issue at storing time and unboxing when the data was retrieved from an instance of ArrayList object.

To take advantage of this article you must have a basic understanding of IDisposable pattern already. Dan Rigsby has recently published a great article on how to implement IDisposable pattern. You will find complete code snippets and download link to the source code on his blog.

There is a misperception about IDisposable that it is used only when you have unmanaged resources declared in classes. The MSDN Library documentation is partially to be blamed for this for mentioning the "unmanaged resources" only not both managed and unmanaged resources