Can't install PSAppDeployToolkit.Tools manually from modules

The Toolkit General Discussion
1

We're unable to use the commands to download from PowershellGallery and have instead been manually importing the required files (e.g. downloading the source .Tools or the .nupkg of a powershell module in PowershellGallery) so that we can Import-Module to the .psd1 for PSADT.Tools

When trying to import the PSAppDeployToolkit.Tools.psd1, it asks for dependencies:

@{ ModuleName = 'Microsoft.PowerShell.Management'; Guid = 'eefcb906-b326-4e99-9f54-8b4bb6ef3c6d'; ModuleVersion = '1.0' }
@{ ModuleName = 'Microsoft.PowerShell.Utility'; Guid = '1da87e53-152b-403e-98dc-74d7b4d63d59'; ModuleVersion = '1.0' }
@{ ModuleName = 'PSAppDeployToolkit'; Guid = '8c3c366b-8606-4576-9f2d-4051144f7ca2'; ModuleVersion = '3.93.0' }
@{ ModuleName = 'PSScriptAnalyzer'; Guid = 'd6245802-193d-4068-a631-8863a4342a18'; ModuleVersion = '1.23.0' }

I've got the first two PS modules and imported PSScriptAnalyzer 1.23.0 successfully but I'm unsure how I get access to the PSADT module of version 3.93.0; I can find an unlisted version 3.9.3 of the module but importing that doesn't meet the dependency requirements when I try and load the .Tools

Has anyone else gone through the process of manually importing the .Tools module and it's dependencies and can see something I'm missing here?

2

During development, PSAppDeployToolkit 3.93.0 was our version number while PSAppDeployToolkit 4.0 was in beta. The version numbers there aren't required versions, their minimum versions.

Please bare in mind that PSAppDeployToolkit.Tools has not been updated to support PSAppDeployToolkit 4.1.x yet, so I'd recommend using it with 4.0.6 for the time being.

3

Thank you for the reply :slight_smile:

I've tried with 4.0.6 just now but can't seem to be facing the same error.

image
image1545×737 40.7 KB

4

Because you're sideloading the modules, you'll probably need to place them directly into C:\Program Files\WindowsPowerShell\Modules as it looks like PSAppDeployToolkit.Tools is assuming the module exists in a $env:PSModulePath location.

I'd report the issue in the GitHub repository here so that it can be logged properly and investigated: GitHub · Where software is built. Its init system will probably have to be reworked to match how I'm initialising things in my PSAppDeployToolkit.WinGet module: PSAppDeployToolkit.WinGet/src/PSAppDeployToolkit.WinGet/ImportsFirst.ps1 at 1809bec5ec04539bd88c505f66322dcb27a2a08e · mjr4077au/PSAppDeployToolkit.WinGet · GitHub.