Custom metadata not retained from NuSpecTemplate

[heaths]

To build a package that supports Chocolatey's guidelines and recommendations, I need to add some package metadata. I see from the targets and task source you can add a $(NuSpecTemplate) pointing to a .nuspec file, but custom metadata is not retained. Seems to be no other way to add custom metadata to projects.

[AArnott]

If it's dropped, I wonder if it's nuget pack that drops it -- or the nuget OM in general.
But we can keep this active while it's true either way.

[heaths]

Digging into this more, it's a problem in NuGet.Packaging. They don't support custom metadata. Any fix would have to be on their side. I've opened NuGet/Home#4751.

[heaths]

If I did fix it on their side (have a few ideas), would you be open to taking a new version? I doubt they'd take a change on 2x but looks like they're already churning on 4.3.

[kovalikp]

Master branch is currently using quite old version of the Nuget (2.X something). I've made a branch some time ago trying to get full support of project.json files (including resolving dependencies), but never got to finish it. But as the 1st step, I did upgrade the NuGet packages to 3.5 in https://github.com/kovalikp/nuproj/tree/wip/json. I guess we should try first, how does NuProj behaves with latest version of NuGet packages.

[AArnott]

Before investing too much, consider #282

[heaths]

Would have to see if they retain custom metadata.

[bbowman]

@kzu would love to know here as well.

[kzu]

There isn't any API in NuGet that allows you to define custom metadata in the nuspec.

If you get such an API introduced there, NuGetizer will happily support it.