Closed rdebath closed 7 months ago
Should be fixed in BcContainerHelper preview as of yesterday
Sorry, nope, it' a nav-docker
issue. New-BCContainer
or Import-TestToolkitToBCContainer
will put the test extensions into an image that doesn't have them but when it tells nav-docker
to put them in the image it's ignored because of that warning.
This is only a speed issue though, next week is more than soon enough.
Got it - you are right, it is not fixed in the latest containerhelper.
This is the fix in nav-docker for this: https://github.com/microsoft/nav-docker/pull/544 Will add a patch to ContainerHelper asap
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
WARNING: Could not find Microsoft.Dynamics.Nav.Apps.Management.psd1
Oh would you look at that; they've broken it again, a couple of days after you fixed it. :unamused:Looks like ...
\program files\Microsoft Dynamics NAV\230\Service\Management\Microsoft.Dynamics.Nav.Apps.Management.psd1
to\program files\Microsoft Dynamics NAV\240\Service\Admin\Microsoft.BusinessCentral.Apps.Management.psd1
And something to do with
Microsoft.Dynamics.Nav.Apps.Management.format.ps1xml
being bodged up too.This specific error means that the image created with either
New-BcImage
orNew-BCContainer
does NOT include the tests, they have to be loaded later which breaks (or slows down) the pipelines.Scripts used to create container and cause the issue
Full output of scripts
Screenshots If applicable, add screenshots to help explain your problem.
Additional context