[ESP] En el siguiente enlace puedes ver leer los cambios relacionados a la versión vigente:
[ENG] In the following link you can read the changes related to the current version:
Más información / More information:
- Github: Microsoft BcContainerhelper
- Powershellgallery: BcContainerHelper 6.1.10 (Updated 2025/12/03)
6.1.10
- Better performance when downloading NuGet packages by adding another cache folder, which defaults to c:\bcnuget.cache
- Add bcnuget to cache parameter in Flush-ContainerHelperCache in order to cleanup NuGet cache folders as well
- Better performance when searching for matching packages by not re-searching multiple times, but instead fetching all versions just once, cached in c:\bcnuget.cache
- Better performance when reading nuspec metadata – cached in c:\bcnuget.cache
6.1.9
- Add support for reportSuppressedDiagnostics in Run-AlPipeline
- Include ‘Application Test Library’ when importing test libraries
6.1.8
- AL-Go issue 1920 Pagescript not working on own github runner
- Issue 4018 Using New-navcontainer with useNewDatabase=true for BC 27 fails
6.1.7
- Issue 3952 Get-AlLanguageExtensionFromArtifacts fails on new BC artifacts
- Add support for TestType field when running tests
- Issue 3943 Error downloading symbols for Microsoft_System
- Add support for RequiredTestIsolation field when running tests
- Catch errors when page scripting tests are failing
6.1.6
- Added a new outcome to failOn = newWarning. For BcContainerHelper it will work as error – in AL-Go for GitHub it will have a meaning.
- Remove support for querying artifacts storage accounts
- Remove setting useIndexForArtifacts – it is always true
- Issue 3938 country code mapping stopped working
6.1.5
- Include AuthContext and Environment in Parameters for InstallMissingDependencies when called from Run-AlPipeline
- Issue 3886 Error on installing apps, app file path is not built correctly from url (ends with «\»)
- AL-Go issue 1695 Fail early if app.json cannot be read
- Issue with BC artifact 27.0.33668.0: app compilation fails because of analyzers not being loaded properly
- Avoid using dotnet 9 for assemblyProbingPaths (for now)
- SymbolsOnly flag is no longer supported in BC27 (issue 1713 on AL-Go for GitHub).
6.1.4
- Issue 3882 Run-AlPipeline with CompilerFolder and Container defined fails when running tests
- Allow running tests in online sandboxes, using CompilerFolder (and ConnectFromHost)
- Add parameter appName to Run-TestsInBcContainer to specify the name of an app in Test Results, if not specified when running against online sandboxes, the appid will be used.
- During Run-AlPipeline, apps which are only published are reported as being installed, which leads to error 1530 in AL-Go repository
- Use standard app filename for app instead of the app name inside the nuget package
- Allow vsixFile to be a local file for New-BCCompilerFolder (3831)
- Fixes issues determining test symbols for W1 and OnPrem artifacts not containing versions in their name (3839)
- Add cache for search results of a NuGet feed
- Add new setting NuGetSearchResultsCacheRetentionPeriod (default: 600) to set the retention period (in seconds) for the search result cache of NuGet feeds (0 to disable the cache)
- Download-BcNuGetPackageToFolder checks all direct dependency versions of a package based on the NuSpec before downloading the whole package and its dependencies
- New Option doNotRemovePackagesFolderIfExists to prevent Run-ALPipeline from deleting the packages folder, if it already exists. Default is false
- Add support for Windows 2025 Containers
- NuGet packageId naming fixes. If a publisher name or app name consists of only UTF8 characters, we would issue an error.
- NuGet packageId naming fixes. If a package id ended up having a minus in front of a period (-.), nuGet would fail on publishing.
6.1.3
- Add setting ExcludeBuilds, which is an array of NuGet range specifications to exclude from Get-BcArtifactUrl. See more about range specification here: https://learn.microsoft.com/en-us/nuget/concepts/package-versioning?tabs=semver20sort#version-ranges
- AL-Go issue 1640 – compiler contains an invalid app template, which needs to be deleted
6.1.2
- Check if app is already installed when publishing to an online environment during CI/CD
- Ensure that tests are running even though a container hasn’t been created
- Allow Run-Alpipeline with CompilerFolder to run tests on an online environment
- AL-Go issue 1542 The process cannot access the file – use runners temp path when running Get-BcArtifactUrl
6.1.1
- Issue 3873 get-bcartifactUrl failes for weekly with UseIndexForArtifacts on non US machines (v6.1)
6.1.0
- Use Artifact Index by default when using Get-BcArtifactUrl
6.0.37
- Removed setting DoNotUseCdnForArtifacts as all download from artifacts store needs to go through FrontDoor
- Add setting UseIndexForArtifacts while working on Artifacts indexing – this setting will be removed and always set to true when indexing functionality is done – please do not use!!!
- AL-Go issue 1519 Submitting to AppSource WARNING: AuthContext.Scopes is .. should be
- Get-BcArtifactUrl -type OnPrem -select all fails after index creation
6.0.36
- Add silent when installing bcreplay npm module
6.0.35
- AL-Go issue 1288 Library apps are not installed if only referenced from test apps
- AL-Go issue 1330 CompilerFolder doesn’t transfer installed Apps to NuGet resolution
- AL-Go issue 1268 Do not throw an un-understandable error during nuGet download
- Use FileStream when uploading per tenant extensions to online environments to support larger apps
- Remove duplicate quotes in new Source and Build elements in apps generated by BcContainerHelper and AL-Go
- Create filesonly build container before enumerating installed apps in Run-AlPipeline
- AL-Go issue 1460 Don’t fail if a dependency is installed in a newer version during build – upgrade if needed
6.0.34
- Compare files before giving a warning about apps with the same name in Run-AlPipeline
6.0.33
- Latest v26 artifacts have lowercase folder names in some areas, breaking New-BcCompilerFolder on Linux
6.0.32
- BcContainerHelper now also loads on PowerShell 7.5.0
6.0.31
- New-BcCompilerFolder with base artifacts doesn’t locate apps in version 25.0 due to a rename of the applications folder (was Applications)
- Run-AlPipeline might try to run tests even though a test app isn’t installed (see https://github.com/microsoft/AL-Go/issues/1405)
6.0.30
- Issue 3762 Give Option to Choose SQL PowerShell Module When Restoring From BacPac
- There are instances where sqlps does not work as expected when it is installed. This change adds a switch parameter, useSqlServerModule, to Restore-BcDatabaseFromArtifacts, New-NavContainer, and the BcContainerHelper config file.
- Issue 1303 from AL-Go repository – renew federated token when access token needs renewal (works only for GitHub at this time)
- Issue 3590 EarliestMatching select option added to Download-BcNuGetPackageToFolder
- Regression when from PR 3760 – Push-BcNuGetPackage doesn’t work on PowerSHell 5
- Issue 3772 Get-BcNuGetPackageId name length limit
- Two new parameter in Sort-AppFoldersByDependencies – selectSubordinates and SkippedApps. If specified, then only the appFolders specified in the first array plus the apps depending on these recursively will be sorted. The remaining folder not included in the sorted appfolders list will be returned in skippedApps.
- Remove some excessive logging
- If Import-TestToolkitToBcContainer was running with useCompilerFolder, then it would require a container to be present at that time.
- Make Run-AlPipeline do just-in-time creation of CompilerFolder and Containers
- Issue 1338 from AL-Go repository: Multi-Project Repository Test App Dependencies Not Resolved
- Issue 3591 When using Publish-NAVApp to publish an app, which fails compilation in the service, the command might hang forever – the fix for this is a temporary hack put in place for the versions which doesn’t work.
- Improve performance and reduce memory consumption when creating and pushing NuGet packages
6.0.29
- Issue 3591 When using Publish-NAVApp to publish an app, which fails compilation in the service, the command might hang forever – the fix for this is a temporary hack put in place for the versions which doesn’t work.
- Improve performance and reduce memory consumption when creating and pushing NuGet packages
6.0.28
- Set useApproximateVersion to true in settings to increase performance of Get-BcArtifactUrl when selecting latest artifact, by using an approximate filtering on blobs
- Regression on Run-AlPipeline, when running containerless compile while having a ImportTestDataInBcContainer registered, would cause an error (AL-Go error 1291 and 1292)
6.0.27
- Issue 3538 Compile-AppWithBcCompilerFolder fails when dependency does propagateDependencies
- Issue 3727 Regression – Release pipelines failing with SaaS environments due BcAuthContext
- Add new overrides to Run-AlPipeline: BackupBcContainerDatabases and RestoreDatabasesInBcContainer for backup up and restoring databases – only parameter transferred is containerName
- Add new parameter to Run-AlPipeline: restoreDatabases, indicating when (during the pipeline execution) a database restore is needed
- Add PageScripting test runner to Run-AlPipeline, adding 4 new parameters: pageScriptingTests, pageScriptingTestResultsFile, pageScriptingTestResultsFolder and doNotRunPageScriptingTests.
- Add BCPT test apps to build artifacts in Run-AlPipeline
6.0.26
- As minimum, always use the generic tag version which was available when shipping BcContainerHelper
- Add awareness of Windows 11 24H2
- Issue #3697 Running tests fails with 401 when running on a BC25 sandbox container with AAD authentication
- Issue #3701 Compile-AppWithBcCompilerFolder, ALTool returns dependencies.appId for older apps
- Wait for databases to be mounted when running Restore-DatabasesInBcContainer
- Include AI Toolkit when copying symbols from container
- Issue 3714 Download-BcNuGetPackageToFolder – throws error when use «-select Exact»
- Issue 3621 New-AadAppsForBc shows «-includeEmailAadApp is deprecated. Use -includeOtherServicesAadApp instead.» but includeOtherServicesAadApp us not setting email permissions
- Issue 3718 Business Central Web Client Fails to Load After Updating to Windows 24H2
- Issue #3703 Missing Function Download-BcEnvironmentInstalledExtensionToFolder
- Fix for issue 1262 in AL-Go for GitHub
- Fix instabilities during Publish-PerTenantExtensionApps
6.0.25
- Fix issue where generateDependencyArtifact doesn’t result in dependencies if useCompilerFolder is true or filesonly containers are used in Run-AlPipeline
- Issue 3686 PowerShell container shortcuts for >= BC24 using wrong PowerShell version
- Issue 3666 Run-AlCops + Run-AlPipeline using outdated appsource default ruleset
- Fix issue where linux executables are missing in the AL Language Extension (use dotnet to execute the commands instead)
- Fix issue where PowerShell sometimes hangs when trying to establish a new PSSession shortly after removing another PSSession (Noticed during end 2 end tests on AL-Go for GitHub)
6.0.24
- Use pre-release altool when running alcops (to be able to get runtime version of nextmajor)
6.0.23
- Issue 3573 GitHub NuGet Handling fails for User Feeds
6.0.22
- Issue #3660 Error about missing ‘azuredevops’ property when using Compile-AppWithBcCompilerFolder
6.0.21
- Main branch is now main instead of master
- Issue 3613 aka.ms/getbc fallback to NAVUserPassword because token expired when setting up SSO
- Issue #3617 Regression File Newtonsoft.Json.dll not found when copying item for New-BcCompilerFolder
- Remove functions for supporting Alpaca and Cloud Containers – integration between alpaca and cloud containers with AL-Go for GitHub will NOT be done through BcContainerHelper
- Issue #2623 New-BcContainer for BC25.1 or BC26 insider with includeTestToolkit AI Test Toolkit dependency missing
- If template for applicationDependency or platformDependency is specified when creating a new BcNuGetPackage, it will create an invalid package if application or platform properties are missing in app.json
- Normalize version strings in nuGetFeed to ensure that NuGet packages with version 1.2.3 are seen as being equal to version 1.2.3.0
- Add Schedule parameter to Publish-PerTenantExtensionApps
6.0.20
- Add trustServerCertificate is the parameter exists in various functions that might be running on the host
- Issue #3594 Run-AlCops says unknown platform version
- Add information about apps excluded due to not being referenced during Publish-BcContainerApp
- Run-AlPipeline to support CompilerFolder and online environments for building and testing
- Added 2 new overrides in Run-AlPipeline: PipelineInitialize and PipelineFinalize
- Add parameter CompilerFolder to Run-TestsInBcContainer and Import-TestToolkitToBcContainer for running tests using CompilerFolder bits from the host
- Replace all occurrences of [System.Runtime.InteropServices.Marshal]::PtrToStringAuto with [System.Runtime.InteropServices.Marshal]::PtrToStringBSTR as the Auto function doesn’t always do what’s expected under Linux
- Ensure correct casing of Newtonsoft.Json.dll for Linux
- Always add extensionId (when specified) to Properties section in test results xml
- If environment is specified as a Web Client URL, and BcAuthContext contains username/password in Run-AlPipeline, then tests will run against this environment. PublishBcContainerApp and ImportTestToolkitToBcContainer needs to be overridden for this to work with full pipeline.
- Including caching of appinfos in CompilerFolder cache (to save time when caching on GitHub Actions)
6.0.19
- Issue #3560 Backup-BcContainerDatabases fails – password must be marked as read only bug
- Issue #3559 ALCops can’t find «Business Foundation» app and doesn’t start because of it
- Support for federated credentials in Azure
- Issue 1093 from AL-Go repo, generateDependencyArtifact doesn’t work when useCompilerFolder is true
6.0.18
- Use altool from prerelease AL Language extension
- Display disk free inside container on error
- Create AppInfo cache on creating a new compiler folder
- Add support for using
TestCodeunitRangeFilterfield inRun-TestsInBcContainerandGet-TestsFromBcContainer - Issue 3206 Auto-Consent the Permissions requested after using New-AadAppsForBc
- Issue 3544 Copy-AlSourceFiles.ps1 does not copy RDLC and DOCS Files with the new report layout definition
- Issue 3550 Run-AlValidation is checking wrong runtime version
- Issue 3555 Increase default timeout
6.0.17
- Issue 3518 If WinRm is not running on the host, a container couldn’t be created
- Issue 3519 New-BcContainer fails due to password complexity on some computers
- Issue 3522 The ‘Expand-Archive’ command was found in the module ‘Microsoft.PowerShell.Archive’,…
- Issue 3523 Copy-FileToBcContainer fails for BcContainerHelper 6.0.16 (added resilience)
6.0.16
- Issue 3477 Regression: Error: App filenames must be unique
- Issue 3478 New-bccontainer fails on BC24 using option -UseNewDatabase
- Allow CustomCodeCops to be a URL for just-in-time download instead of a file shared with the container
6.0.15
- Issue 3467 Can’t create a backup of a container with the Backup-BCContainerDatabases commandlet
- Use PowerShell 5 in places where invoke-sqlcmd or other functions from the SqlServer PowerShell module are used
6.0.14
- Issue 3465 Regression: Flush-ContainerHelperCache calculates wrong CacheFolder
6.0.13
- Issue 3452 Error when running Run-AlValidation : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
- Issue 3454 DockerDo : Cannot bind argument to parameter ‘imageName’ because it is an empty string.
- Issue 3354 Regression : Compile Folder removal of symbols folder fails: The process cannot access the file
- Issue 3460 Do not install SqlServer PowerShell module
6.0.12
- Issue 3432 New-BcContainerWizard stopped working after generic images with ltsc2016, ltsc2019 and ltsc2022 was introduced
- Make parameters in Copy-AppFilesToFolder mandatory
- Support .zip files in folders in Copy-AppFilesToFolder
- Issue 3431 Run-TestsInBcContainer, Get-TestsFromBcContainer and Run-ConnectionTest doesn’t work if container is using SSL
- Issue 3427 New-BCContainer in version 6.0.11 failed to run completely
- Issue 3444 Container Creation fails at «Installing ASP.NET Core 1.1»
6.0.11
- Issue 3420 New-BcImage uses hyperv even if it is disabled
- Issue 3411 Run-AlPipeline: Exception calling «Parse» with «1» argument(s): «String » was not recognized as a valid DateTime.
6.0.10
- Issue 3415 Use process isolation
6.0.9
- Issue 3404 New-BcContainerBcUser fails with ‘Invoke-SqlCmd’ error when running BC24
- Remove support for pre 1.0.2.15 generic images
- Issue 3406 Regression – Set-BcContainerKeyVaultAadAppAndCertificate only worked when running pwsh in container
- Issue 3407 Export-NavContainerDatabasesAsBacpac fails using PS7x (and with tenants on BC24 altogether)
- Issue 3409 Invoke-RestMethod -SkipCertificateCheck for PowerShell 7
- By default use mcr.microsoft.com/businesscentral:ltscXXXX instead of mcr.microsoft.com/businesscentral:10.0.osbuild.osrevision as generic image
6.0.8
- Fix error where Publish-BcNuGetPackageToContainer doesn’t work with BC 24
6.0.7
- Issue 3347 Download-BcNuGetPackageToFolder to support package description for app name if title is not specified
- Support dependency version templates on NuGet packages
- Issue 3349 NuGet package files section name is wrong when using azure blob storage direct download url
- Issue 3358 Run-TestsInBcContainer using Windows Authentication doesn’t work if exactly one user exists in the tenant
- Fix error in Get-BcContainerAppInfo in NextMajor
- Check-BcContainerHelperPermissions didn’t work on PS7
- Issue #3379 Adding -installCertificateOnHost to New-BcContainer didn’t work when running PS7 (silently failed)
- Issue #3376 Regression – Download-Artifacts stopped downloading pre-requisites
- Issue 3371 Unable to get companyname from Windows Users when running tests
- Disallow invoking Run-ALPipeline with
keepContainerwithout specifying credentials to use - Issue 3369 Patch images version 1.0.2.15 with an updated installer
- Add awareness of Windows 11 23H2
- Patch images version 1.0.2.15 with an updated prompt.ps1, which loads PowerShell 7 modules when running pwsh
- Add new setting usePwshForBC24, which is default true to instruct Invoke-ScriptInBcContainer to use pwsh (PS7) instead of powershell (PS5) when invoking scripts in BC 24+ containers
- Add parameter usePwsh to Open-BcContainer and Invoke-ScriptInBcContainer, defaulted to the value of the usePwshForBC24 setting
6.0.6
- Include Microsoft_Business Foundation Test Libraries.app when importing test libraries (and tests)
- Include Microsoft_System Application Test.app and Microsoft_Business Foundation Tests.app when importing tests
- Bug when running Publish-BcContainerApp against a cloud container ($authContext not defined)
- Remove the need for a Container when using Replace-DependenciesInAppFile (containername parameter is now obsolete)
- Two new parameters on Sort-AppFilesByDependencies (includeSystemDependencies and includeDependencyVersion)
- Add Public Microsoft NuGet Feeds as settings constants
- Fix issues in Download-BcNuGetPackageToFolder, where extensive amounts of NuGet searches was performed to locate packages
- Download-BcNuGetPackageToFolder now returns an array of apps downloaded instead of True/False
- JIT install PowerShell 7 in container when using BC version 24 or above (if not already installed in container)
- JIT install ASP.NET Core 1.1 when using BC 15 – 18 on Generic 1.0.2.15 or above
6.0.5
- Proof of concept support for hosting artifacts as Universal Packages
- Add new function Get-BcNuGetPackageId to get a NuGet Package Id based on publisher, name, id and version
- Issue 3301 Run-AlValidation fails running AppsourceCop «Could not load type ‘System.Object’ from assembly ‘System.Private.CoreLib’
- Give better error message if GitHub CLI, GIT or dotnet is not installed
- Issue 3301 Run-AlValidation fails running AppsourceCop «Could not load type ‘System.Object’ from assembly ‘System.Private.CoreLib’ (Regression in 6.0.4)
- Issue 3313 Strange error in Copy-BcEnvironment
- Issue 3318 Download-BcNuGetPackageToFolder fails when no dependencies defined
- Add Stacktrace output to high level functions Download-BcNuGetPackageToFolder and Get-BcNuGetPackage
- Fix for AL-Go issue 913 (https://github.com/microsoft/AL-Go/issues/913)
- Issue 3322 Default country for nextminor and nextmajor should be w1, not whatever country was the last one generated
- Encoding problems when using Invoke-ScriptInBcContainer with PowerShell 7.4.1
6.0.4
- Rename AppInfoCache.json to cache_AppInfo.json (which by default is covered by .gitignore in AL-Go for GitHub)
- Refactor NuGet feed functionality to use NuGetFeed class
- Add trusted NuGet feeds to settings to allow searching for NuGet packages in all trusted feeds
- Support searching for Earliest, Latest, Exact or Any NuGet package (default is Latest)
- Reset startcount when using Restart-BcContainer
- Issue 3277 Run-ALCops uses wrong CodeAnalysis dll path
- Add support for useDevEndpoint in Run-AlPipeline when importing test toolkit
- New function Get-AppJsonFromAppFile to extract the app.json file from an app (also from a runtime package)
- New function Copy-AppFilesToFolder to copy or download and unpack all apps from an array of .zip or .app files and place them in a folder
- New function Create-SymbolsFileFromAppFile to create a symbols only app file from an app file
- New switch on Run-AlPipeline, enableCodeAnalyzersOnTestApps, to enable CodeCops and other code analyzers on test apps
Preview 6.0.6
- –
Más information/ More information:



Deja un comentario