Add attributes from .nuspec to project.json schema #1302
Comments
We're missing licenseUrl and copyright but the rest are available. We need to update the project.json schema. |
Icon appears to be missing as well. It would be nice to have a way to set the title too. Currently it just sets it to the "raw" name but I usually set a friendly name in my NuGet packages (eg. ID = "React.Web.Mvc4", Name = "ReactJS.NET (MVC 4 and 5)") |
I'm not a fan of title but I understand that people do use it. |
@conniey I also assume that by signing, you mean strong naming? |
@davidfowl Authenticode and strong name signing. Issue #621 seems to cover the authenticode scenario. Do you have any plans on adding StrongName signing? |
We currently have plans to strong name everything by default with a key that cannot be configured. This is mostly to support scenarios where people need to interop with desktop as our CoreCLR loader ignores strong naming. |
The owners property is also not supported. Currently the value from authors is copied into this field when the nuget package is created. Other non-supported fields are: |
This is all done in beta4. ReleaseNotes haven't been added because it's weird 😄 |
The standard Nuspec properties are now part of the project.json which are used to build the nuget package output. See: aspnet/dnx#1302
project.json seems to unify (packages.config, *.nuspec and dependencies in *.csproj). But, it is lacking some .nuspec attributes that may be useful to enterprise developers.
I am developing a library using ASP.NET vNext but it is a hassle to automate the signing/upload of this package because I have to unzip it, add signed dlls, and re-write the .nuspec with a template.
Useful Attributes:
The text was updated successfully, but these errors were encountered: