Bunian on Emad Alashi

Beware of Static Constructors

Fri, 06 Feb 2009 22:39:22 +0000

In Bunian we needed to use a static constructor for some reason, it was all going good; we tested the code and it ran smoothly…excellent (Code Coverage anyone?!).
But when I came across this situation, it appeared that the static constructor wasn’t invoked!even when “Class.Method();” is called! so lets examine it.

I have two simple classes as an Example:

    public class Parent
  
    {
  
        public static string DoSomething()
  
        {
  
            return “Parent: DoSomething() called”;
  
        }
  
    }

    public class Child : Parent
  
    {

Get On With It!

Fri, 16 Jan 2009 15:56:35 +0000

When we started gathering requirements from the charity organizations for Bunian, it appeared that there are other kinds of people who benefit from the charity organization; there are “needy families” whose father is still alive but can’t sustain their families, and “students” who can’t afford their study.

So Bunian needs to support all these Beneficiaries in smart way; we solved the problem by creating the IBeneficiary interface. But the problem is that in order to get out with the best solution ever (damn perfectionism!), we kept coming up with different solutions, and overriding them with other solutions every once in a while, and this kept going like forever!

Importance of Documentation

Fri, 26 Dec 2008 11:25:15 +0000

Lately we have decided in Bunian to move on to NHibernate 2.0, and the contributor assigned to the move started out, only to send an email one day after: “THERE IS NO DOCUMENTATION!’.
We had errors as a result to the move which couldn’t be fixed without a documentation explaining why this happened.

After searching for a while, we found two resources of the new documentation:

a wiki help that is hosted on Google Knol:
http://knol.google.com/k/fabio-maulo/-/1nr4enxv3dpeq/21#
Not really appealing to be used extensively; no smooth flow between chapters, frames dazzle the eyes, no table of contents, but surely a great step forward for a documentation that is maintained by the community