Closed General-Fault closed 4 years ago
Hi @General-Fault - this is a behavior of the underlying packaging technology (Nuget). It is discussed in depth over in this issue: https://github.com/PowerShell/DscResources/issues/508
@PlagueHO Thank you. I just figured this out myself when the problem disappeared after updating the PowerShellGet package provider.
This package is published in PowerShell Gallery with version 2.12.0, however the module version is 2.12.0.0. Consequentially, the module is is installed to "C:\Program Files\WindowsPowerShell\Modules\PSDscResources\2.12.0\". This does not precisely match the release version number (note the missing ".0"). Unfortunately this causes a problem when this module is referenced by specific version.