How to Set Up a New Business Central Development Project – The 100% Correct Way
This guide covers the essential setup steps for creating a new Business Central AL development project, from project creation and app.json configuration to code analysis and DevOps. It emphasizes starting with proper templates, modern naming conventions, and AL-Go for GitHub to ensure maintainability, CI/CD readiness, and AppSource compatibility.
Read it hereOpen in Claudehttps-stefanmaron-com-posts-how-to-set-up-a-new-business-central-development-project--cc8dba8c26.md
post Stefan Maron
Key points
- Start from a template such as the AL-Go for GitHub templates instead of the default AL: Go! command, remove demo objects and download symbols
- Configure app.json carefully: a sensible ID range (not starting at 50000 for PTEs), a version not tied to BC releases, explicit runtime and application versions, and only needed dependencies
- Use PascalCase names with the registered affix as a suffix plus a short project code; namespaces with the affix as top level can remove the need for affixes in object names
- Enable CodeCop, AppSourceCop, PerTenantExtensionCop, UICop and LinterCop, with an AppSourceCop.json per app and external rulesets to balance PTE and AppSource rules
- Set up AL-Go early for build, test and deploy automation, including ruleset settings and scheduled test workflows
Context
- Features: AL-Go for GitHub, CodeCop, AppSourceCop, PerTenantExtensionCop, UICop, LinterCop, external rulesets, namespaces
- Versions: June 2025
Source: Stefan Maron, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.