---
id: video/QT3RKx9rGJA
type: video
title: AL Go for GitHub January Office Hour
summary: AL-Go for GitHub January 2025 office hour. Version 6.3 added conditional settings on build mode, preprocessor symbols, removal of temporary "this build" artifacts and versioning strategy 3. Incremental builds were an open PR expected in preview within weeks. The Q&A covered NuGet and GitHub Packages dependencies, scheduled publishing, self-hosted runners, dotnet sign code signing, configuration packages and local dev environments.
tier: official
language: en
tags:
  - al-go
  - conditional settings
  - build modes
  - preprocessor symbols
  - versioning strategy
  - artifacts
  - performance
  - compiler
  - incremental builds
  - workflow
  - scheduling
  - dependencies
system: platform
review:
  state: reviewed
  by: opus
  at: "2026-10-07T23:02:23.430Z"
  flags: []
generated:
  at: "2026-10-07T23:02:23.494Z"
  pipeline: 0.2.0
  prompts:
    extract-video: 1
    summarize-video: 2
  input_hash: a47ad5c0e0dbc398354d7811a0c7c7c91df40bf4b7092ff9f9acd09ac0218021
evidence:
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=109s
    title: "Conditional Settings on Build Mode: generally available"
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 109
    quote: we released version 6.3 there were like four uh things in that one besid some some fixes and stuff like that the conditional settings
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=926s
    title: "Incremental Builds: preview"
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 926
    quote: we're expecting that one to get in uh preview within the next few uh weeks
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=109s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 109
    quote: in the latest month we released version 6.3 there were like four uh things in that one
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=184s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 184
    quote: if the build mode is next major then use these settings like override what's in the uh settings file normally
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=381s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 381
    quote: now it's actually major minor build if you use versioning strategy 3 that comes from uh your app Jason and then only the revision
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=561s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 561
    quote: if you if you said that you want to use compiler folder um and you use a container you'll actually be compiling using the
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=849s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 849
    quote: there is an PR called incremental builds that one will only build the the apps that are changed or uh depends on apps that
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=926s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 926
    quote: we're expecting that one to get in uh preview within the next few uh weeks
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1180s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 1180
    quote: we're also working on figuring out if we can run the P scripting tasks as part of deployment so when you're deploying to a
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1291s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 1291
    quote: Al go for GitHub does support nuget both like as a as a provider and as a consumer of nou packages
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1650s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 1650
    quote: if you use the setting called generate dependency artifacts uh then in the buildt artifacts there will be a a an artifact called um
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1753s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 1753
    quote: these office hours calls we're going to do them monthly uh this year except for July and December
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1907s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 1907
    quote: there are two settings that determines uh which Runners you use there's the GitHub Runner which determines what uh what Runners are being used
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1948s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 1948
    quote: the update ELO system files will always use the GitHub hosted Runner and the reason for that is that if your self-hosted Runner is
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2141s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2141
    quote: some cases very large apps will in order to be published into a into a container actually use quite a bit of memory
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2210s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2210
    quote: is that it often looked as a developer tool instead of a tool to maintain a well ro running bc implementation
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2309s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2309
    quote: you can have a different configuration package if you're running the tests for us version for Danish version and for Italy version
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2398s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2398
    quote: what we utilize for for this is net sign um for doing the signing and and if if doet sign can sign your app
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2494s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2494
    quote: reshipping them but we know they'll be going away so we be deprecating the conflict packages
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2514s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2514
    quote: we're not going to ship our extended demo data as contct packages we're going to ship that as absence
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2572s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2572
    quote: Telemetry data from Alo quite a lot is recorded and we can already evaluate various things for ourselves especially PRS
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2672s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2672
    quote: we've decided on net sign and we'll until until further proof prove that that's the wrong way we'll stick to that
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2819s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 2819
    quote: old pte are remaining published but uninstalled in extensions list after deployments gets a little cluttered
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3060s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 3060
    quote: that's I think an organizational level can be forced at least it's forced for Microsoft organization
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3181s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 3181
    quote: you can use what's called Federated pretentions or you can use um an a app that has access to the keyword
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3339s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 3339
    quote: a w1 version of your app and then you can have an italy and a danish version of the app
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3482s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 3482
    quote: after we merge the incremental builds pr that comes in preview in the next few weeks
  - kind: video
    url: https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3636s
    title: AL Go for GitHub January Office Hour
    date: "2025-02-03T09:27:10.000Z"
    commit: null
    t: 3636
    quote: license that is included in the artifacts is a perfectly good development license and you don't need to
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
video_id: QT3RKx9rGJA
channel: yt-microsoft
source_name: Microsoft Dynamics 365 Business Central (YouTube)
url: https://www.youtube.com/watch?v=QT3RKx9rGJA
published_at: "2025-02-03T09:27:10.000Z"
duration_s: 3721
captions: full
audience:
  - developer
  - administrator
  - partner
chapters:
  - t: 0
    title: Introduction and Meeting Setup
  - t: 109
    title: Conditional Settings and Build Modes
  - t: 241
    title: Removal of This Build Artifacts
  - t: 360
    title: New Versioning Strategy (v3)
  - t: 457
    title: Opening Q&A Session
  - t: 529
    title: Performance and Compiler Optimization Questions
  - t: 652
    title: Workflow Branch Usage and Multi-Branch Updates
  - t: 749
    title: Environment Publishing and Scheduling
  - t: 849
    title: Incremental Builds Feature
  - t: 947
    title: Office Hours Format and Directions Sessions
  - t: 1056
    title: AL Go Sample Repositories and Documentation
  - t: 1149
    title: Results Viewer and Page Scripting Tasks
  - t: 1264
    title: External Dependencies and NuGet Feeds
  - t: 1370
    title: Local Development Container Features
  - t: 1468
    title: Scheduled Deployment and NuGet Publishing Model
  - t: 1583
    title: Dependency Artifacts and Build Outputs
  - t: 1753
    title: Office Hours Schedule and Audience Engagement
  - t: 1886
    title: Self-hosted Runners and Workflow Configuration
  - t: 2020
    title: Self-hosted Runner Setup and Hardware Recommendations
  - t: 2210
    title: AL Go Adoption and Organizational Value
  - t: 2281
    title: Test Data Deployment and Configuration Packages
  - t: 2364
    title: Code Signing and Certificate Management
  - t: 2474
    title: Configuration Packages and Demo Data Apps
  - t: 2572
    title: AL-Go Telemetry and KQL Queries
  - t: 2652
    title: Signing Tool Choices and Net Sign Commitment
  - t: 2762
    title: Installation Ease and Extension Cleanup
  - t: 2885
    title: Training and Workshops for AL-Go
  - t: 3035
    title: Single Sign-On for GitHub Migration
  - t: 3108
    title: Documentation Roadmap and Key Vault Credential Setup
  - t: 3249
    title: AL-Go Repository and Project Architecture
  - t: 3380
    title: Dependency Management and Repository Organization
  - t: 3462
    title: Incremental Builds for Multi-Project Repositories
  - t: 3524
    title: Local Development Environment with Multiple Projects
  - t: 3614
    title: Licensing Requirements for AppSource Development
features:
  - name: Conditional Settings on Build Mode
    status: ga
    t: 109
    verified: true
    status_source: video
  - name: Preprocessor Symbols
    status: unclear
    t: 127
    verified: false
    status_source: video
  - name: Removal of This Build Artifacts
    status: unclear
    t: 241
    verified: false
    status_source: video
  - name: Versioning Strategy 3
    status: unclear
    t: 360
    verified: false
    status_source: video
  - name: Compiler Folder for Container Builds
    status: unclear
    t: 541
    verified: false
    status_source: video
  - name: Use Workflow From Branch
    status: unclear
    t: 652
    verified: false
    status_source: video
  - name: Scheduled Publish to Environment
    status: unclear
    t: 749
    verified: false
    status_source: video
  - name: Incremental Builds
    status: preview
    t: 849
    verified: true
    status_source: video
  - name: Results Viewer for Page Scripting Tasks
    status: unclear
    t: 1149
    verified: false
    status_source: video
  - name: Page Scripting Tasks in QA Deployment
    status: unclear
    t: 1149
    verified: false
    status_source: video
  - name: NuGet Feed Support for External Dependencies
    status: unclear
    t: 1264
    verified: false
    status_source: video
  - name: Local Development Container with Private Repositories
    status: unclear
    t: 1370
    verified: false
    status_source: video
  - name: Publishing to NuGet Feed Model
    status: unclear
    t: 1468
    verified: false
    status_source: video
  - name: Generate Dependency Artifacts
    status: unclear
    t: 1637
    verified: false
    status_source: video
  - name: Self-Hosted Runner Support for All Workflows
    status: unclear
    t: 1886
    verified: false
    status_source: video
  - name: Configuration Packages for Test Data
    status: unclear
    t: 2281
    verified: false
    status_source: video
  - name: Import Test Data NPC Container Override
    status: unclear
    t: 2329
    verified: false
    status_source: video
  - name: Dotnet Sign Integration for Code Signing
    status: unclear
    t: 2364
    verified: false
    status_source: video
  - name: Configuration Packages Deprecation
    status: unclear
    t: 2494
    verified: false
    status_source: video
  - name: AL-Go Telemetry Module
    status: unclear
    t: 2572
    verified: false
    status_source: video
  - name: Commitment to Net Sign
    status: unclear
    t: 2652
    verified: false
    status_source: video
  - name: Extension Cleanup on Deployment
    status: unclear
    t: 2762
    verified: false
    status_source: video
  - name: AL-Go Workshop
    status: unclear
    t: 2885
    verified: false
    status_source: video
  - name: Single Sign-On Enforcement
    status: unclear
    t: 3035
    verified: false
    status_source: video
  - name: Key Vault Credential Configuration
    status: unclear
    t: 3181
    verified: false
    status_source: video
  - name: Multi-Project Repository Support
    status: unclear
    t: 3249
    verified: false
    status_source: video
  - name: GitHub Packages for Dependency Resolution
    status: unclear
    t: 3400
    verified: false
    status_source: video
  - name: Local Development Environment in AL-Go
    status: unclear
    t: 3524
    verified: false
    status_source: video
objects_mentioned:
  - other app.json
  - other settings file
  - other GitHub business Central apps algo office hours 202
  - other project branch dependencies
  - other update ELO system files
  - other net sign
  - other AL 4.2
  - other configuration packages
  - other Key Vault
  - other Cronos license
quotes:
  - t: 109
    text: in the latest month we released version 6.3 there were like four uh things in that one
    check: exact
  - t: 184
    text: if the build mode is next major then use these settings like override what's in the uh settings file normally
    check: exact
  - t: 381
    text: now it's actually major minor build if you use versioning strategy 3 that comes from uh your app Jason and then only the revision
    check: snapped
  - t: 561
    text: if you if you said that you want to use compiler folder um and you use a container you'll actually be compiling using the
    check: exact
  - t: 849
    text: there is an PR called incremental builds that one will only build the the apps that are changed or uh depends on apps that
    check: snapped
  - t: 926
    text: we're expecting that one to get in uh preview within the next few uh weeks
    check: exact
  - t: 1180
    text: we're also working on figuring out if we can run the P scripting tasks as part of deployment so when you're deploying to a
    check: exact
  - t: 1291
    text: Al go for GitHub does support nuget both like as a as a provider and as a consumer of nou packages
    check: exact
  - t: 1650
    text: if you use the setting called generate dependency artifacts uh then in the buildt artifacts there will be a a an artifact called um
    check: exact
  - t: 1753
    text: these office hours calls we're going to do them monthly uh this year except for July and December
    check: exact
  - t: 1907
    text: there are two settings that determines uh which Runners you use there's the GitHub Runner which determines what uh what Runners are being used
    check: exact
  - t: 1948
    text: the update ELO system files will always use the GitHub hosted Runner and the reason for that is that if your self-hosted Runner is
    check: snapped
  - t: 2141
    text: some cases very large apps will in order to be published into a into a container actually use quite a bit of memory
    check: exact
  - t: 2210
    text: is that it often looked as a developer tool instead of a tool to maintain a well ro running bc implementation
    check: fuzzy
  - t: 2309
    text: you can have a different configuration package if you're running the tests for us version for Danish version and for Italy version
    check: exact
  - t: 2398
    text: what we utilize for for this is net sign um for doing the signing and and if if doet sign can sign your app
    check: exact
  - t: 2494
    text: reshipping them but we know they'll be going away so we be deprecating the conflict packages
    check: fuzzy
  - t: 2514
    text: we're not going to ship our extended demo data as contct packages we're going to ship that as absence
    check: exact
  - t: 2572
    text: Telemetry data from Alo quite a lot is recorded and we can already evaluate various things for ourselves especially PRS
    check: exact
  - t: 2672
    text: we've decided on net sign and we'll until until further proof prove that that's the wrong way we'll stick to that
    check: exact
  - t: 2819
    text: old pte are remaining published but uninstalled in extensions list after deployments gets a little cluttered
    check: exact
  - t: 3060
    text: that's I think an organizational level can be forced at least it's forced for Microsoft organization
    check: exact
  - t: 3181
    text: you can use what's called Federated pretentions or you can use um an a app that has access to the keyword
    check: exact
  - t: 3339
    text: a w1 version of your app and then you can have an italy and a danish version of the app
    check: fuzzy
  - t: 3482
    text: after we merge the incremental builds pr that comes in preview in the next few weeks
    check: fuzzy
  - t: 3636
    text: license that is included in the artifacts is a perfectly good development license and you don't need to
    check: fuzzy
---

# AL Go for GitHub January Office Hour

> AL-Go for GitHub January 2025 office hour. Version 6.3 added conditional settings on build mode, preprocessor symbols, removal of temporary "this build" artifacts and versioning strategy 3. Incremental builds were an open PR expected in preview within weeks. The Q&A covered NuGet and GitHub Packages dependencies, scheduled publishing, self-hosted runners, dotnet sign code signing, configuration packages and local dev environments.

[Watch on YouTube](https://www.youtube.com/watch?v=QT3RKx9rGJA) · Microsoft Dynamics 365 Business Central (YouTube) · 2025-02-03 · 1:02:01 · tier official · reviewed (checked by Opus)

## Overview

This is a 62-minute AL Go for GitHub office hour, published 2025-02-03. It opens with the changes in the latest release (6.3): conditional settings based on build mode, preprocessor symbols, removal of "this build" artifacts, and versioning strategy 3, where major, minor and build come from app.json and only the revision comes from the run number.

The rest is Q&A. Topics include compiler folder builds, using a workflow from another branch, scheduled publish to environment, incremental builds, NuGet feeds and dependency artifacts, self-hosted runners, configuration packages and test data, code signing, telemetry, single sign-on, Key Vault credentials, and multi-project repositories with local development.

## Key points

- Conditional settings can override the settings file when a given build mode is active, for example next major.
- With versioning strategy 3, major, minor and build come from app.json and only the revision comes from the run number. Run attempts no longer increment the version on rebuild.
- The temporary "this build" artifacts for multi-project repositories are removed. Normal artifacts are now produced and can be used to test before a pull request is approved.
- Incremental builds, which build only changed apps and the apps that depend on them, were described as a pull request expected to reach preview within a few weeks. Changes to low-level apps still rebuild dependents.
- Self-hosted runners for all workflows are configured with two settings: the GitHub Runner setting for build jobs and runs-on for other workflows. The update AL-Go system files workflow always uses a GitHub-hosted runner.
- Code signing uses dotnet sign (net sign). The team will not accept pull requests proposing other signing approaches, but may accept settings that support additional CA vaults.
- Local dev environments work for only one project at a time. They need GitHub permissions to read all dependencies, and GitHub packages are not supported there.

## Chapters

- [0:00](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=0s) Introduction and Meeting Setup
- [1:49](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=109s) Conditional Settings and Build Modes
- [4:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=241s) Removal of This Build Artifacts
- [6:00](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=360s) New Versioning Strategy (v3)
- [7:37](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=457s) Opening Q&A Session
- [8:49](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=529s) Performance and Compiler Optimization Questions
- [10:52](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=652s) Workflow Branch Usage and Multi-Branch Updates
- [12:29](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=749s) Environment Publishing and Scheduling
- [14:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=849s) Incremental Builds Feature
- [15:47](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=947s) Office Hours Format and Directions Sessions
- [17:36](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1056s) AL Go Sample Repositories and Documentation
- [19:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1149s) Results Viewer and Page Scripting Tasks
- [21:04](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1264s) External Dependencies and NuGet Feeds
- [22:50](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1370s) Local Development Container Features
- [24:28](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1468s) Scheduled Deployment and NuGet Publishing Model
- [26:23](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1583s) Dependency Artifacts and Build Outputs
- [29:13](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1753s) Office Hours Schedule and Audience Engagement
- [31:26](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1886s) Self-hosted Runners and Workflow Configuration
- [33:40](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2020s) Self-hosted Runner Setup and Hardware Recommendations
- [36:50](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2210s) AL Go Adoption and Organizational Value
- [38:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2281s) Test Data Deployment and Configuration Packages
- [39:24](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2364s) Code Signing and Certificate Management
- [41:14](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2474s) Configuration Packages and Demo Data Apps
- [42:52](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2572s) AL-Go Telemetry and KQL Queries
- [44:12](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2652s) Signing Tool Choices and Net Sign Commitment
- [46:02](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2762s) Installation Ease and Extension Cleanup
- [48:05](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2885s) Training and Workshops for AL-Go
- [50:35](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3035s) Single Sign-On for GitHub Migration
- [51:48](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3108s) Documentation Roadmap and Key Vault Credential Setup
- [54:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3249s) AL-Go Repository and Project Architecture
- [56:20](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3380s) Dependency Management and Repository Organization
- [57:42](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3462s) Incremental Builds for Multi-Project Repositories
- [58:44](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3524s) Local Development Environment with Multiple Projects
- [1:00:14](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3614s) Licensing Requirements for AppSource Development

## Features

| Feature | Status | At | Evidence |
|---|---|---|---|
| Conditional Settings on Build Mode | generally available, demoed | [1:49](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=109s) | "we released version 6.3 there were like four uh things in that one besid some some fixes and stuff like that the conditional settings" ([1:49](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=109s)) |
| Preprocessor Symbols | status not stated, demoed | [2:07](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=127s) |  |
| Removal of This Build Artifacts | status not stated, demoed | [4:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=241s) |  |
| Versioning Strategy 3 | status not stated, demoed | [6:00](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=360s) |  |
| Compiler Folder for Container Builds | status not stated | [9:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=541s) |  |
| Use Workflow From Branch | status not stated | [10:52](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=652s) |  |
| Scheduled Publish to Environment | status not stated | [12:29](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=749s) |  |
| Incremental Builds | preview | [14:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=849s) | "we're expecting that one to get in uh preview within the next few uh weeks" ([15:26](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=926s)) |
| Results Viewer for Page Scripting Tasks | status not stated | [19:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1149s) |  |
| Page Scripting Tasks in QA Deployment | status not stated | [19:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1149s) |  |
| NuGet Feed Support for External Dependencies | status not stated | [21:04](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1264s) |  |
| Local Development Container with Private Repositories | status not stated | [22:50](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1370s) |  |
| Publishing to NuGet Feed Model | status not stated | [24:28](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1468s) |  |
| Generate Dependency Artifacts | status not stated | [27:17](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1637s) |  |
| Self-Hosted Runner Support for All Workflows | status not stated | [31:26](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1886s) |  |
| Configuration Packages for Test Data | status not stated | [38:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2281s) |  |
| Import Test Data NPC Container Override | status not stated | [38:49](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2329s) |  |
| Dotnet Sign Integration for Code Signing | status not stated | [39:24](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2364s) |  |
| Configuration Packages Deprecation | status not stated | [41:34](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2494s) |  |
| AL-Go Telemetry Module | status not stated | [42:52](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2572s) |  |
| Commitment to Net Sign | status not stated | [44:12](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2652s) |  |
| Extension Cleanup on Deployment | status not stated | [46:02](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2762s) |  |
| AL-Go Workshop | status not stated | [48:05](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2885s) |  |
| Single Sign-On Enforcement | status not stated | [50:35](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3035s) |  |
| Key Vault Credential Configuration | status not stated | [53:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3181s) |  |
| Multi-Project Repository Support | status not stated | [54:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3249s) |  |
| GitHub Packages for Dependency Resolution | status not stated | [56:40](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3400s) |  |
| Local Development Environment in AL-Go | status not stated | [58:44](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3524s) |  |

## AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

- other "app.json" at [3:04](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=184s)
- other "settings file" at [3:04](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=184s)
- other "GitHub business Central apps algo office hours 202" at [17:47](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1067s)
- other "project branch dependencies" at [27:30](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1650s)
- other "update ELO system files" at [32:28](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1948s)
- other "net sign" at [39:58](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2398s)
- other "AL 4.2" at [41:14](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2474s)
- other "configuration packages" at [41:34](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2494s)
- other "Key Vault" at [53:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3181s)
- other "Cronos license" at [1:00:36](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3636s)

## Quotes

- [1:49](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=109s) "in the latest month we released version 6.3 there were like four uh things in that one"
- [3:04](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=184s) "if the build mode is next major then use these settings like override what's in the uh settings file normally"
- [6:21](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=381s) "now it's actually major minor build if you use versioning strategy 3 that comes from uh your app Jason and then only the revision"
- [9:21](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=561s) "if you if you said that you want to use compiler folder um and you use a container you'll actually be compiling using the"
- [14:09](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=849s) "there is an PR called incremental builds that one will only build the the apps that are changed or uh depends on apps that"
- [15:26](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=926s) "we're expecting that one to get in uh preview within the next few uh weeks"
- [19:40](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1180s) "we're also working on figuring out if we can run the P scripting tasks as part of deployment so when you're deploying to a"
- [21:31](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1291s) "Al go for GitHub does support nuget both like as a as a provider and as a consumer of nou packages"
- [27:30](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1650s) "if you use the setting called generate dependency artifacts uh then in the buildt artifacts there will be a a an artifact called um"
- [29:13](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1753s) "these office hours calls we're going to do them monthly uh this year except for July and December"
- [31:47](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1907s) "there are two settings that determines uh which Runners you use there's the GitHub Runner which determines what uh what Runners are being used"
- [32:28](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1948s) "the update ELO system files will always use the GitHub hosted Runner and the reason for that is that if your self-hosted Runner is"
- [35:41](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2141s) "some cases very large apps will in order to be published into a into a container actually use quite a bit of memory"
- [36:50](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2210s) "is that it often looked as a developer tool instead of a tool to maintain a well ro running bc implementation"
- [38:29](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2309s) "you can have a different configuration package if you're running the tests for us version for Danish version and for Italy version"
- [39:58](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2398s) "what we utilize for for this is net sign um for doing the signing and and if if doet sign can sign your app"
- [41:34](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2494s) "reshipping them but we know they'll be going away so we be deprecating the conflict packages"
- [41:54](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2514s) "we're not going to ship our extended demo data as contct packages we're going to ship that as absence"
- [42:52](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2572s) "Telemetry data from Alo quite a lot is recorded and we can already evaluate various things for ourselves especially PRS"
- [44:32](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2672s) "we've decided on net sign and we'll until until further proof prove that that's the wrong way we'll stick to that"
- [46:59](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2819s) "old pte are remaining published but uninstalled in extensions list after deployments gets a little cluttered"
- [51:00](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3060s) "that's I think an organizational level can be forced at least it's forced for Microsoft organization"
- [53:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3181s) "you can use what's called Federated pretentions or you can use um an a app that has access to the keyword"
- [55:39](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3339s) "a w1 version of your app and then you can have an italy and a danish version of the app"
- [58:02](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3482s) "after we merge the incremental builds pr that comes in preview in the next few weeks"
- [1:00:36](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3636s) "license that is included in the artifacts is a perfectly good development license and you don't need to"

## Disclaimers in the video

- [13:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=781s) coming-later: right now you cannot do a sketch on that... there is a mechanism to do that by creating a small yo file... I'll create document for how to do that as well
- [14:29](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=869s) preview: there is an PR called incremental builds that one will only build the the apps that are changed
- [15:26](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=926s) preview: incremental builds PR expected to get in preview within the next few weeks
- [19:19](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1159s) preview: results viewer for Alo for GitHub is being worked on
- [19:40](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1180s) preview: working on figuring out if we can run page scripting tasks as part of deployment
- [20:01](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1201s) coming-later: I'll expect the results viewer to be done before we ship version seven in April
- [20:22](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1222s) preview: page scripting test and QA requires investigation due to MFA compatibility issues
- [25:43](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1543s) coming-later: publishing to NuGet feed model being talked about maybe a year or two from now
- [26:23](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1583s) subject-to-change: documentation sample on how to do that and and add that and I think I promised do that within the next two weeks so expect that to be done
- [27:46](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=1666s) coming-later: something we could do in the future instead of building actually just taking things from the repo
- [40:18](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2418s) coming-later: if you find that net sign can do what you need but you need like to add another um setting or whatever to to to support other CA vaults as well uh please work with us and we might be able to actually include that in Alo
- [41:34](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2494s) coming-later: we know they'll be going away so we be deprecating the conflict packages
- [42:52](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2572s) preview: it's a very like relatively new like module in Alo
- [48:23](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=2903s) subject-to-change: that one probably needs some some love and attention as well
- [51:48](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3108s) coming-later: future topics is for the future and like we give rebates tomorrow is what it says in the shop wall
- [58:02](https://www.youtube.com/watch?v=QT3RKx9rGJA&t=3482s) preview: incremental builds PR that comes in preview in the next few weeks

Presenters (as heard): Maria, Alexander, Todd, Thomas, Florian, Mik, Sebastian, Philip, Ronan, Emanuel, Floren, Eric.