Manual install not working from nupkg file

[Fiander]

Details of the scenario you tried and the problem that is occurring

when doing a download from https://www.powershellgallery.com/packages/xPSDesiredStateConfiguration/8.8.0.0 and then doing an install-module from my own repository, the module gets installed in the wrong folder. it gets installed in : C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\8.8.0 instead of C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\8.8.0.0

import-module does not find the module until i rename the folder from 8.8.0 to 8.8.0.0

i have tried more versions ( 8.4.0.0, 3.3.0.0, and they all have the same problem. the nupkg file is also named wrong ( .8.8.0. instead of .8.8.0.0. )

Verbose logs showing the problem

Suggested solution to the issue

somewhere in the auto build process of the nupkg file the version in the name is not correct.

The operating system the target node is running

OsName : Microsoft Windows Server 2019 Datacenter OsOperatingSystemSKU : DatacenterServerEdition OsArchitecture : 64-bit WindowsVersion : 1809 WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434 OsLanguage : en-US OsMuiLanguages : {en-US}

Version and build of PowerShell the target node is running

PSVersion 5.1.17763.1
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.1
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Version of the DSC module that was used ('dev' if using current dev branch)

master

Im in a offline enviroment, and can not provide logs or screendumps.

[PlagueHO]

Thanks for raising this - this is actually a larger issue with Nuget, but it is being tracked over here: https://github.com/PowerShell/DscResources/issues/508

We do still need a fix for this problem, but will require us modifying the deployment process for the modules (which I understand will happen).