As we mentioned in Chapter 5, Developing a Customized Solution for Dynamics 365 Business Central, extension A cannot reference objects and methods exposed by extension B. This is only possible if extension A explicitly declares a dependency on extension B.
When moving an existing solution to extensions, you have two main choices:
- Create a single monolithic extension
- Create N dependent extensions
Let's explore these concepts in more detail.
A single monolithic extension is an easier choice since developers don't have to think about independent modules. Instead, they just create all the objects and business logic in a single giant AL extension project. In the end, there will be a single .app file that does the following:
- Adds new objects
- Extends standard objects
- Adds new business logic
- Raises events
- Subscribes to events...
