Our goal was the development of a framework which integrates the experiences we collected in our last projects. It should be easy to handle for end users, administrators and also easy to adapt and extend by developers.

We summed up common functionalities of our last software development projects and defined them as standard features for Cuberry. Beside user management and input validation we also had the entity life cycle management (we call it workflow) and the easy deployment of new and updated modules on top of our list of standard functionalities. The localization/globalization of the application was also one of the most important objectives in our scope.

We wanted to have as many customizable elements as possible for the future administrators but we also want to keep the code readable to make it easy for developers to understand and adapt it. So we had to strike a balance between code complexity and features.
For the solution we wanted to reuse as much available code and as many standard DLLs as possible.

So we found out that the PRISM is exactly what we needed to base our framework on. The Microsoft Enterprise Library was used for error logging and history tracking.

For printing we wanted to have a user friendly solution, so we decided to use the Word ML standard and local Microsoft SQL Reports.
For simplicity reasons we kept the solution on WPF instead of using Silverlight and web services.

We hope you find Cuberry useful for your needs and will appreciate every feedback. We welcome suggestions for improvement and are open for new ideas.

If you would like to join the Cuberry development team please contact us at contact@cuberry.net.

Wish you a happy programming.