tag:help.appveyor.com,2012-11-13:/discussions/questions/3975-whats-correct-way-to-setup-nuget-analyzer-package-buildAppVeyor: Discussion 2018-08-25T02:17:17Ztag:help.appveyor.com,2012-11-13:Comment/425746002017-05-22T08:56:02Z2017-05-22T08:56:07ZWhat's correct way to setup NuGet analyzer package build<div><p>Hi, should I expect any answer?<br>
Will it help if I paid for some time of premium account?</p></div>Leonid Tsarevtag:help.appveyor.com,2012-11-13:Comment/425746002017-05-22T17:33:54Z2017-05-22T17:33:54ZWhat's correct way to setup NuGet analyzer package build<div><p>No need to pay :) We were not able to find quick solution for you. Will try one more time in day or two and will update you.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/425746002017-05-25T11:06:18Z2017-05-25T11:06:20ZWhat's correct way to setup NuGet analyzer package build<div><p>Ilya, any updates on this?</p></div>Leonid Tsarevtag:help.appveyor.com,2012-11-13:Comment/425746002017-05-25T17:00:08Z2017-05-25T17:00:08ZWhat's correct way to setup NuGet analyzer package build<div><p>Hi Leonid,</p>
<p>I forked your repo and tried to make it work with <code>nuget pack <name>.nuspec</code>, but without a luck. I believe that yes, you have to replace version on the fly with custom script inside <code>.nuspec</code> file. Simple string replace can be done easily with PowerShell.<br>
Then you have to use custom <code>after_build</code> script to run <code>nuget pack <name>.nuspec</code>, and also add your <code>.nuspec</code> files to <a href="https://www.appveyor.com/docs/packaging-artifacts/">artifacts</a>.</p>
<p>I still believe that it may exist a better way, but I just do not know it. Maybe you can reach nuget people on GitHub and ask them, how to make nuget to respect <code>$version$</code> and substitute it with data from AssemblyInfo when you are calling <code>nuget pack <name>.nuspec</code> and not <code>.csproj</code></p>
<p>Ilya.</p></div>Ilya Finkelshteyn