Self Hosted NuGet Repository

Known Issues

I personally use Sonatype Nexus Repository OSS for testing. What I have come across is a difference in the way the PSGallery interprets and install PS Modules. The PS Gallery will read the module manifest for install, while Sonatype Nexus a from what I have read other NuGet hosted repositories will use the generated nuspec file.

This becomes an issue as a module manifest is not required to adhere to the same Semantic Version schema that is required/expected in the Nuget Nuspec standard. The result is the file path version for the module, not matching what is in the module manifest, and PowerShell will not import the module.

As a temporary solution I have modified the 2 currently effected modules. cChoco and RunAsUser and uploaded them for use.

LogoGitHub - jyonke/cChocoExGitHub

Further Details

LogoNuGet pack ignores nuspec versions [unwanted version normalization?] 路 Issue #3050 路 NuGet/HomeGitHub
LogoNuGet Package Version Referencedocsmsft

Opened Issues

LogoModule Manifest/Nuspec Version Mismatch 路 Issue #26 路 KelvinTegelaar/RunAsUserGitHub
LogoModule Manifest/Nuspec Version Mismatch 路 Issue #161 路 chocolatey/cChocoGitHub
PreviousInstallationNextStart-cChocoEx

Last updated

Was this helpful?