diff --git a/.github/ISSUE_TEMPLATE/nav-2018--bc-spring-2018--12-x---bc-fall-2018--13-x--issues.md b/.github/ISSUE_TEMPLATE/nav-2018--bc-spring-2018--12-x---bc-fall-2018--13-x--issues.md deleted file mode 100644 index 7e25e60..0000000 --- a/.github/ISSUE_TEMPLATE/nav-2018--bc-spring-2018--12-x---bc-fall-2018--13-x--issues.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -name: NAV 2018, BC Spring 2018 (12.X), BC Fall 2018 (13.X) Issues -about: "\U0001F6D1\U0001F6D1\U0001F6D1Please contact customer support\U0001F6D1\U0001F6D1\U0001F6D1" -title: '' -labels: customer-support -assignees: '' - ---- - -This GitHub repository is dedicated to handling issues and feedback for the latest Developer Preview releases of the AL development tools for Dynamics 365 Business Central. - -If you can reproduce the problem on the latest Business Central Developer preview version we will be happy to look further into it. Otherwise please contact the regular support channel. - -You can open Support Request to CSS through PartnerSource portal or contact your Service Account Manager (SAM) in the local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also step by step direct you how to open a support request or how to get credentials if this is the first time for you / your company. - -For more details please read: -https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/ -https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions#i-found-an-issue-on-nav-2018-what-do-i-do diff --git a/ISSUE_TEMPLATE b/ISSUE_TEMPLATE index 5be0b5d..2539a92 100644 --- a/ISSUE_TEMPLATE +++ b/ISSUE_TEMPLATE @@ -1,10 +1,10 @@ diff --git a/README.MD b/README.MD index 0e63a0b..cd30c74 100644 --- a/README.MD +++ b/README.MD @@ -19,9 +19,9 @@ Bugs pertaining to the AL compiler and the developer tools for the latest versio See the [triage process](https://github.com/Microsoft/AL/wiki/Triage-Process) document for more information on how we handle incoming requests. -## Community +## Support and community -Our answers to frequently asked questions can be found in our [FAQ](https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions). To get help from community members please use one of the following resources: +For issue routing, diagnostics, and performance guidance, see [Support and diagnostics](SUPPORT.md). To get help from community members please use one of the following resources: - [Business Central Community](https://community.dynamics.com/business/f/758) - [Yammer groups for partners](https://aka.ms/BCYammer) diff --git a/SUPPORT.md b/SUPPORT.md new file mode 100644 index 0000000..730ae86 --- /dev/null +++ b/SUPPORT.md @@ -0,0 +1,71 @@ +# Support and diagnostics + +This repository accepts reproducible defects in the latest AL Language extension, compiler, +static analyzers, debugger, test tooling, and other AL developer tools. + +For the complete intake guidance, see [Contributing](CONTRIBUTING.md#reporting-issues). + +## Choose the right channel + +- Report a reproducible defect in the latest AL developer tools in this repository. +- Report supported-product runtime, application, or platform issues through + [Business Central support](https://learn.microsoft.com/dynamics365/business-central/product-help-and-support). +- Request first-party application extensibility through the + [BCApps issue intake](https://github.com/microsoft/BCApps/issues/new/choose). +- Submit feature requests and static-analysis rule suggestions through + [Business Central Ideas](https://aka.ms/bcideas). +- Report security vulnerabilities according to the [security policy](SECURITY.MD). + +## Report a tooling bug effectively + +Before opening an issue: + +1. Use the latest AL Language extension and search existing issues. +2. Disable other Visual Studio Code extensions. +3. Provide a minimal, copyable AL sample or a small repository that reproduces the problem. +4. Include the expected and actual behavior, AL Language, Visual Studio Code, Business Central, + and operating-system versions. + +Use the [Developer Experience bug template](.github/ISSUE_TEMPLATE/al-developer-experience-bug.md) +for the complete checklist. + +## Understand analyzer diagnostics + +| Prefix | Analyzer | Purpose | +| --- | --- | --- | +| `AA` | CodeCop | Code quality, readability, and localizability | +| `AS` | AppSourceCop | AppSource compliance and upgrade compatibility | +| `PTE` | PerTenantExtensionCop | Per-tenant extension requirements | +| `AW` | UICop | Web client UI compatibility | + +Use the diagnostic ID to find the relevant [AL code analysis documentation](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-using-code-analysis-tool). +Configure rule severity with a [ruleset](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-using-code-analysis-tool-with-rule-set). +AppSourceCop and PerTenantExtensionCop must not be enabled together. + +## AI-assisted AL development + +The AL Language extension and the +[AL Development Tools package](https://www.nuget.org/packages/Microsoft.Dynamics.BusinessCentral.Development.Tools/) +support AI-assisted AL development: + +- Visual Studio Code Language Model Tools for interactive use with GitHub Copilot. +- AL MCP Server (`altool launchmcpserver`) for MCP-compatible agents, headless automation, and + CI/CD scenarios. +- AL LSP Server (`altool launchlspserver`) for semantic navigation such as definitions, + references, completions, rename, and type hierarchy. + +See [AI agent tools for AL development](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/al-agent-tools/al-agent-tools-overview) +and the [AL Development Tools package](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-al-tool-package). + +When reporting a problem, include the Development Tools or AL Language version, agent host, command +or transport, minimal workspace, and sanitized diagnostic log. Never include authentication tokens or +customer data. + +## Investigate performance + +For a slow AL development environment, start with +[Optimizing Visual Studio Code for AL development](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-optimize-visual-studio-code). + +For Business Central application performance, use the +[developer performance guidance](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/performance/performance-developer), +Page Inspection, the AL Profiler, and telemetry to gather evidence before reporting a tooling defect.