nupkg extension to consider something a valid nuget package. Obviously the PowerShell PackageManagement CMDLets are not relying strictly on a. It only worked on some packages made with "cpack". ![]() Worked perfect on packages actually created by "nuget pack". So I used that command, along with choco push, to download => push => delete temp local copy, repeat. The only nuget tool that allowed "download only" (no install, no extraction) that I could find is PowerShell 5's packagemanagement command "Save-Package" So I have created a package pump / sync script for migrating that runs on a client. (And couldn't anyway if both were linux)įYI - This probably affects other migration / sync scenarios as well (including artifactory). Nexus's package store is not plain *.nupkg files - whether Windows or not - so this can't be done from server side. ![]() Now I am just going through a package migration from a Nexus Repository Windows Server to a Nexus Repository Linux Server. In this case I setup a powershell on the proget server and read the entire pack volume and shoved it into nexus with push commands ![]() I have already done Proget (windows only) => Nexus on Windows.
0 Comments
Leave a Reply. |