Chapter 6. Anti-patterns and Handling Legacy Code

From the perspective of Architectural and Design Patterns and coding guidelines, Microsoft Dynamics NAV is very consistent, but even though the Patterns have always been the secret source, the product is not always nice and clean. Many developers have worked on solutions for many years with or without guidelines about the maintainability and upgradability of the patterns.

The Dynamics NAV application from scratch has been built in quite a neat and clean way, but throughout the years, modules that Microsoft acquired through acquisition or sub-contracting have been added. They have not always been cleaned up, and following the rules that we learned in the earlier chapters of this book.

We call this phenomenon legacy code, and since our ecosystem is three decades old, there is a lot of it.

From a business perspective, it is hard to get a budget to spend a few years in a basement, changing your legacy code, which has been working...