Module based applications

Right from the beginning in this industry everyone talks about applications made from modules and that they are the way to go when developing applications (that are not oriented to the embedded world, that is a totally different story).

There are many good reasons why an application based on modules on long term is preferred in the detriment of  single module applications and I’m going to enumerate some of them:

1. Distributed development – in case of a modularized application a group of developers an split up the work more nicely based on module priority, size, difficulty, etc.
2. Versioning – this is one of the features that not all application handle in a decent manner. A lot of applications (most of them that were not designed with this purpose in mind) cannot be updated to a new version only if you actually come with another executable (set of files) and overwrite the existing one, this implying more work for both the client and the producer of this files. A modular application on the other hand can just update part of this modules without the need of reinstalling the whole application (of course this is not possible all the time, but with a good design, it should work in 99,99% of the times).

I will post here a small sample on how you can achieve this using a small C# sample.

(to be continued)