I am using NuGet.exe to pack up a directory of files and it seems that it ignores any directory that starts with a dot. Even when I try to explicitly use the "files" entry in the nuspec file, it won't let me include that directory or any of the files within it.
Is there a way to override this behavior?
Here is my command line: NuGet.exe pack ..\build\MyPackage.nuspec -OutputDirectory "\someserver\blah" -basePath "c:\temp\packageStaging" -Version "3.0" -NoPackageAnalysis
The reason for NoPackageAnalysis is that I am making a non standard package for use in Octopus deploy.
Click “Advanced System Settings” then click the “Environment Variables” button located within the Advanced tab. From here double-click the PATH variable in the top panel and create a new entry by adding the path to the directory that contains your NuGet.exe file (in this instance it's C:/NuGet/).
Install the official nuget.exe in your PC. Create a Symbolic Link here: %localappdata%\microsoft\winget\links. Make the nuget.exe globally available for your user to call it from anywhere, since the aforementioned directory should be present in your user's PATH variable.
nuget folder is used as a cache for packages downloaded to speed up project restore and compilation. It can safely be removed. Worst case, it will have to download the packages again in the future. Follow this answer to receive notifications.
you could use -NoDefaultExcludes option of nuget.exe
more details here: http://docs.nuget.org/docs/reference/command-line-reference NoDefaultExcludes Prevent default exclusion of NuGet package files and files and folders starting with a dot e.g. .svn.
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