That’s a mouthful, isn’t it :-)?
As you might have figured in quite some sessions, threads and posts, I’m quite fond running docker images on a remote Hyper-V on my laptop. From the moment it was described by Arend Jan, I’m using it. In my opinion, it’s a much better way to run, because Windows Server is so much better in memory management as Windows 10 is (in regards of Docker that is).
And let’s not quote Ed Stark here ;-). A disadvantage of working like this is that you have to “remote” PowerShell in two machines:
That why I created new PowerShell modules – just to make that a bit easier. I described it earlier this year here.
I shouldn’t tell you about the txt2al conversion tool. It’s the tool that converts txt-files to al. Obviously, this tool is part of normal the NAV environment, so after Freddy already created some functions in the navcontainerhelper to be able to use the tool from a docker host – I created my own function to do that for a remote dockerhost ;-).
I think there are two scenarios where this tool is useful:
That’s why I created the function “Export-RDHNAVApplicationObjectsAsAL” and made that part of the “CRS.RemoteNAVDockerHostHelper” module on the PowerShell Gallery.
And it turns out I use it all the time :-). Here is just one example where I can export all reports as AL.
$containerName = 'devpreview'
$Path = 'C:\Temp\Reports'
$result = Export-RDHNAVApplicationObjectsAsAL `
-DockerHost $DockerHost `
-DockerHostCredentials $DockerHostCredentials `
-DockerHostSessionOption $DockerHostSessionOption `
-ContainerName $containerName `
-Path $Path `
-extensionStartId 50000 `
-filter 'Type=3' #All Reports