Book Image

Learning Dynamics NAV Patterns

By : Marije Brummel
Book Image

Learning Dynamics NAV Patterns

By: Marije Brummel

Overview of this book

Microsoft Dynamics NAV is a complete ERP system, which also contains a robust set of development tools to support customization and enhancement. These include an object designer for each of the seven application object types, a business application-oriented programming language with .NET interface capability, a compiler, a debugger, and programming testing language support. Learning Dynamics NAV Patterns will guide you through the NAV way of solving problems. This book will first introduce you to patterns and the software architecture of the NAV and then help you to build an example application. Then, it walks you through the details of architectural patterns, design patterns, and implementation patterns. This book will also talk about anti-patterns and handling legacy code. Finally, it teaches you to build solutions using patterns. Proven patterns and best practices will help you create better solutions that are easy to maintain in larger teams across several locations. It will guide you through combining abstract patterns using easy-to-understand examples and will help you decide which patterns to use in which scenarios.
Table of Contents (9 chapters)
Thank you for buying Learning Dynamics NAV Patterns

The boy scout rule

Refactoring can be very complex, time consuming, and can lead to disruption in the release cycles. It should therefore be handled with care and tested thoroughly.

When applications have big pieces of legacy code, the question often rises of where to start and when to implement the methodology, as discussed in this book.

A simple rule is to leave the objects that you touch in better condition than when you started working on them. This rule, however, conflicts with the rule of only refactoring without changing the application.

Refactoring can lead to errors that did not exist before. Making mistakes is what makes us human. Refactoring should therefore never be done as a part of bug fixing.