Remove SilentlyContinue from Publish-BcNuGetPackageToContainer

[aholstrup1]

❔What, Why & How

Background
In BC28 there seems to be some issues with PS Remote Session which are used during Invoke-ScriptInBcContainer. If BCContainerHelper fails to create a remote session, it's supposed to fall back to docker exec.

This issue
AL-Go ships with an override to InstallMissingDependencies. The override will call Publish-BcNuGetPackageToContainer -ErrorAction SilentlyContinue. Publish-BcNuGetPackageToContainer will call Get-BcContainerServerConfiguration which relies on Invoke-ScriptInBcContainer

When Invoke-ScriptInBcContainer is called like this, it will silently fail to initialize the management module in the PSSession.

(Partial) Mitigation
A mitigation to this particular problem would be to replace the ErrorAction with a try catch and a warning indicating that the app could not be published. Without the ErrorAction, BCContainerHelper will fall back to docker exec and the workflow will continue.

This should mitigate the impact in the linked issue while we're investigating a fix for the root cause.

Related to issue: #2145

✅ Checklist

• Add tests (E2E, unit tests)
• Update RELEASENOTES.md
• Update documentation (e.g. for new settings or scenarios)
• Add telemetry

[Copilot]

Pull request overview

Mitigates BC28 dependency publishing issues by avoiding -ErrorAction SilentlyContinue when publishing NuGet dependencies into a BC container, so BCContainerHelper can fall back to docker exec, while keeping the pipeline running with a warning if publishing still fails.

Changes:

• Replaced -ErrorAction SilentlyContinue with try/catch around Publish-BcNuGetPackageToContainer.
• Emits an OutputWarning including the exception message when publishing fails.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.