Appendix C: Resources and Further Reading
Objectives
By the end of this appendix you will be able to:
- Use a curated learning path based on your AL maturity level
- Select resources by skill goal (syntax, architecture, testing, integration)
- Build an ongoing practice routine using this book and external references
- Plan how to grow as a contributor, from learner to reviewer
C.1 Toolchain setup matrix
| Goal | Primary tool | Why it matters |
|---|---|---|
| Author AL objects | Visual Studio Code + AL extension | Core development workflow |
| Publish/debug extension | Business Central sandbox + debugger | Safe runtime validation |
| Validate behavior | AL test codeunits | Regression protection |
| Collaborate | GitHub issues/PRs | Shared review and improvement loop |
C.2 Curated learning path
Beginner track
- Chapters 1 to 3 (foundation and setup)
- Chapters 4 to 6 (language basics)
- Chapters 7 to 9 (table/page/codeunit architecture)
Intermediate track
- Chapter 10 (reporting)
- Chapter 11 (packaging and permissions)
- Chapter 12 (integration patterns)
- Chapters 13 to 15 (performance, testing, security)
Advanced/contributor track
- Chapter 16 (case-study synthesis)
- Chapter 17 (advanced extensibility patterns)
- Chapter 18 (quality contributions)
C.3 Recommended references
C.4 Practice and contribution routine
- Weekly: implement one chapter task end to end.
- Biweekly: add or improve one regression test.
- Monthly: submit one contribution with validation evidence.
- Quarterly: review one external AL repository and write down what you learned.
Appendix summary
You now have a map of resources tied to concrete AL goals and a staged learning plan that takes you from beginner to contributor. The routine in C.4 gives you a regular practice schedule to keep improving.
Tasks
- Path selection. Choose a track and list your next three chapters.
- Resource mapping. Pair one external resource with each selected chapter.
- Try it yourself. Draft a 4-week practice plan using C.4 cadence.
Check your work: your plan should include implementation, validation, and contribution activity—not reading alone.