As already stated, BcContainerHelper uses c:\programdata\bccontainerhelper and NavContainerHelper uses c:\programdata\navcontainerhelper. The obvious ones are the folders and the configuration variable. You should be able to do that using: Install-Module -Name PowerShellGet -Repository PSGallery -Force DifferencesĪ few things have changed between NavContainerHelper and BcContainerHelper.
If PowerShell tells you that -allowPrerelease isn’t a known parameter, you will need to update your version of PowerShellGet. Should give you the latest prerelease version (1.0.1-preview143 while starting to write this blog post) Install-Module BcContainerHelper -force -allowPrerelease Should give you the latest stable version of BcContainerHelper (1.0.0 while writing this blog post). Like with NavContainerHelper, installing the latest version is easy Install-Module BcContainerHelper -force While writing this blog post version 1.0.2 is the latest build and insider builds of BcContainerHelper 1.0.3 are being deployed with every successful build (CD) with a prerelease tag/build number and any bug fix will be available as soon as it has been checked in the containerhelper pipeline. Only bug fixes which are blocking for people who for some reason cannot move to BcContainerHelper yet. NavContainerHelper will from now only get bug fixes and not all bug fixes.
New features will ONLY be added to BcContainerHelper and 1.0.2 is shipped now with terminology changes to use Bc instead of Nav where it makes sense. In a future version I will add an information stating that people should move to BcContainerHelper in order toīcContainerHelper 1.0.0 has been shipped with exactly the same functionality as NavContainerHelper 0.7.0.21. NavContainerHelper will stay for people finding things on blogs and trying things out.
Development and PRs to NavContainerHelper has stopped and only bug fixes to keep pipelines running will be approved. Primary reason for this is, that people can stay on the latest NavContainerHelper until they have to move due to functionality they need. It was important to have the change to artifacts done before the rename. Adding this to NavContainerHelper was a bit scary and I decided to do this with the move to BcContainerHelper. With BcContainerHelper the default location of the work directory becomes c:\programdata\bccontainerhelper but I have also added a way to modify the location of the caches and shared folders/files. NavContainerHelper is hardcoded to c:\programdata\navcontainerhelper and as you can imagine, changing this could cause some disruption. Directory changeĪ frequent feature request I have received is the ability to control where the module will place its files. As explained in this blog post, I needed to shift to SemVer 1.0. In order to start submitting prereleases I needed a different versioning schema. Ideally the insider could break occasionally and the stable would never. The stable version should be used by everyone else. The insider (preview) should be used by people who work closely with docker and pipelines, people who want to have the latest and greatest and people who want to contribute to the functionality, performance and stability of the module.
80 pipelines/people managed to download the faulty version before a new version was available.Īt that time I realized that I had to find a way to have a stable and an insider version of the containerhelper. I do have a lot of tests running with every release of the module, but things can go wrong and 3 weeks ago I shipped a version called 0.7.0.12 which would have broken every single Business Central pipeline based on NavContainerHelper if I hadn’t released a fix within 45 minutes. NavContainerHelper is widely used and pipelines all over the world rely on NavContainerHelper not to fail. Why the change then?īeside the obvious reason, that the product is called Business Central and not NAV, there are a few other reasons why I wanted to start a new module in the PowerShell Gallery. Both modules contain the same functions and BcContainerHelper can do the same things as NavContainerHelper.
Although you can install both modules side by side, the function names will clash and you will only get yourself into problems. īcContainerHelper is a replacement for NavContainerHelper. BcContainerHelper is another PowerShell module available in the PowerShell Gallery here. Existing pipelines using NavContainerHelper can continue running – no problem just yet.įuture innovations and changes to support future versions of Business Central might require you to switch to BcContainerHelper. Before you read anything, please understand that NavContainerHelper is still available in the PowerShell gallery and it will still be available for the foreseeable future.