NuGet.Packer

NuGet.Packer copied to clipboard

Even though I specified it explicitly both in the `Package.nuspec` file and the assembly information? How do I specify the version number myself?

ghost

Respect content files with "Copy to output directory" set to "Copy if newer" or "Copy always"

1

I am encountering the same issue as described here: https://stackoverflow.com/questions/21143817/set-content-files-to-copy-local-always-in-a-nuget-package/30386836#30386836 I basically have a `sqlite.dll` binary file which is at the root of the project, as a content file that...

mayerwin

Visual Studio 2017 support

1

Request support for Visual Studio 2017. Visual Studio 2017 changed some things, and as a result a newer version of Nuget.exe (v4+) is required or user get build errors like:...

JVimes

Add ability to generate NuGet spec from the package manager console

1

Would be nice to have a quick way to move from a .nuspec-less NuGet.Packer project to creating a .nuspec file to customize the resulting package. Would be nice to have...

jchadwick

Integrate NuGet.Packer into Visual Studio via an extension

1

Per @mayerwin in #9: > Publishing a Visual Studio extension that would piggyback on NuGet.Packer (if found present in project files), to provide the functionality of manually generating/publishing the package...

jchadwick

Support ability to pull version number from AssemblyVersionAttribute

1

Quoting @mayerwin from #10: > The standard usage with nuget pack *.csproj is to use the assembly's version number as the NuGet package version number. People trying to switch to...

jchadwick

First, thank you so much for publishing this plugin! It is exactly what I was looking for. Simple and efficient. It would really deserve to be highlighted in NuGet's official...

mayerwin