This project has moved. For the latest updates, please go here.

Is it also possible to define the licenseUrl and projectUrl using the Config.ps1?

Aug 17, 2014 at 11:08 AM
Edited Aug 17, 2014 at 11:26 AM
Is it also possible to define the licenseUrl and projectUrl using the Config.ps1?

In the nuspec this is possible, how to do this using Config.ps1 file ?
Coordinator
Aug 18, 2014 at 6:53 PM
No, it's not possible to define those in the Config.ps1. The only .nuspec values that you can specify in the Config.ps1 are the Version Number and Release Notes. This was done on purpose, as pretty much all of the other .nuspec values are constant, but the Version Number and Release Notes values are likely to change with every package created.
Marked as answer by deadlydog on 8/19/2014 at 7:43 AM
Aug 19, 2014 at 2:08 PM
OK Clear.

Actually I asked this question because I want to do this:

1] Define a .nuspec file which describes the licenseUrl, projectUrl and release notes
2] Let newnugetpackage create a nuget package file based on 1 and automatically add the dependencies
3] The version from the nuget package should match the version from the AssemblyInfo.cs

Points 1 and 2 work fine, but for point 3 this does not work because the version from the .nuspec file is always used ?
Coordinator
Aug 19, 2014 at 3:43 PM
For point 3, in your .nuspec file make sure the value for the version element is $version$. This will have it pull the version number from the assembly version. See this page for more info on replacement tokens in the nuspec file. And just make sure you leave the $versionNumber variable in Config.ps1 blank (as it is by default).
Aug 19, 2014 at 6:24 PM
Thanks for your help!