Move my Chocolatey apps to another PC

Ahh, I have always enjoyed meta programming, so when I was thinking about how to get my Chocolatey apps from one PC to another, the choice was easy: A small Powershell command to create a Powershell script to install my apps somewhere else.

It’s a oneliner that loops the installed Chocolatey apps via the “choco list” command and generates a list of strings.

choco list -lo -r -y | % { "choco install $($_.SubString(0, $_.IndexOf("|"))) -y" } | Out-File Install.ps1

This is how the output looks on my machine:

choco install 7zip -y
choco install 7zip.install -y
choco install beyondcompare -y
choco install chocolatey -y
choco install chocolatey-core.extension -y
choco install chocolateygui -y
choco install docker-for-windows -y
choco install DotNet4.5.2 -y
choco install DotNet4.6.1 -y
choco install Firefox -y
choco install git -y
choco install git.install -y
choco install httrack.app -y
choco install KB2919355 -y
choco install KB2919442 -y
choco install openra -y
choco install PowerBI -y
choco install python3 -y
choco install resharper-platform -y
choco install sabnzbd -y
choco install sharpkeys -y
choco install sublimetext3 -y
choco install visualstudiocode -y
choco install vlc -y
choco install vscode -y
choco install win32diskimager -y
choco install win32diskimager.install -y

Quite easy to setup a new PC, thanks to the power of PowerShell and Chocolatey 🙂

Another extension for VS Code to your Toolkit

The SQL Server extension for Visual Studio Code is a nice way of avoiding SQL Server Management Studio for when you need to do some light SQL’ing while working in VS Code

https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql

You can do queries directly from VS Code even with awesome intellisense and nice formatting.

VS Code is getting closer and closer to becoming a one-stop destination for all the things we need to with NAV and Business Central.

The type 5056 was not defined for the function

This happens if you have a table object, saved with a post-GDPR CU (Like NAV2018 CU6), imported that object into a pre-GDPR NAV and then try to export it to TXT from that version. Post-GDPR objects include the DataClassification properties

Make sense? Post-GDPR objects are not compatible with Pre-GDPR NAV CUs.

The solution, do not mix your development environment. Currently, that means that CU2 is the preferred CU for NAV2018 development.

(The quick fix, is the remove the fields, and RETYPE them (Cut’n’Paste will not work).

I’ve seen a couple of explanations about this, but they seemed incomplete, so I did this quick write-up.

This is part of a very old C/Side bug, (or feature might some people from Microsoft argue) where unknown properties are carried along behind the scenes when importing FOB files.