Menu
I created a nuget package using the pack command:
http://docs.nuget.org/docs/reference/command-line-reference#Pack_Command
everything works fine; the only issue that I have is related to the fact that I'm trying to install a certificate through a powershell script. The name of this certificate is something like "CompanyName Ltd.pfx" (note the blank space) but in the nuget package it is encoded as "CompanyName%20Ltd.pfx" and therefore my installation script fails for this certificate. Now, this is a minor issue as I can modify the certificate name removing the blank space, but anyway I'm wondering if there is a method that prevents (or controls) this type of encoding (as I haven't found anything in the nuget documentation).
293
Put simply, a NuGet package is a single ZIP file with the . nupkg extension that contains compiled code (DLLs), other files related to that code, and a descriptive manifest that includes information like the package's version number.
The default is %userprofile%\. nuget\packages (Windows) or ~/. nuget/packages (Mac/Linux). A relative path can be used in project-specific nuget.
The NuGet Visual Studio extension, the NuGet Package Manager Console, and the NuGet command-line tool all make use of the NuGet configuration file, which by default is located under %AppData%\NuGet\NuGet. config.
The above process will clear all the NuGet packages from cache location. So once cleared the NuGet cache location then every NuGet package will be downloaded/restored from source location to cache location again.
I had the exact same problem. Unzipping the file does seem to encode the file names no matter what utility you use.
I solved this by opening the .nupkg in the NuGet Package Explorer and using Export from the File-menu.
94
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
