tag:help.appveyor.com,2012-11-13:/discussions/problems/1459-appveyoryml-and-assembly-info-patchingAppVeyor: Discussion 2018-10-19T08:16:59Ztag:help.appveyor.com,2012-11-13:Comment/359271112015-01-31T13:40:33Z2015-01-31T13:40:34Zappveyor.yml and assembly info patching<div><p>Hi guys,</p>
<p>couple of notes on the assembly info patching.</p>
<p>First, the yml export is incorrect. It suggests that file:
'**\AssemblyInfo.*' will work if such a value was used previously
on the web site. Unfortunately, you need to double the \. Very
confusing.</p>
<p>Secondly, there is no feedback on if patching did anything at
all, only at the end of a build can u see if it happened. It'd be
awfully useful to know what files were found if any.</p>
<p>Thirdly, I tend to use / in paths as it's a vaid path separator
on windows and every other commonly-used platform, but the assembly
patcher doesn't support that, which is a shame.</p>
<p>Lastly, the documentation suggests simply using
"AssemblyInfo.*". It may well be a PBKAC, but when building a
solution, that doesn't appear to work on my solutions.</p>
<p>Hope it helps.</p>
<p>@serialseb</p></div>Sebastien Lamblatag:help.appveyor.com,2012-11-13:Comment/359271112015-01-31T15:59:36Z2015-01-31T15:59:36Zappveyor.yml and assembly info patching<div><p>Great findings - thanks for reporting that! Will do more tests
and fix the issues.</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/359271112015-02-02T21:36:23Z2015-02-02T21:36:24Zappveyor.yml and assembly info patching<div><p>I am having similar issues trying to work out if anything has
been patched sucessfuly.<br>
I always get: Patching AssemblyInfo...OK but clearly nothing has
been.</p></div>Matt Davistag:help.appveyor.com,2012-11-13:Comment/359271112015-02-05T05:19:49Z2015-02-05T05:19:49Zappveyor.yml and assembly info patching<div><p>We've added more status messages while patching assembly infos.
Sample output:<br>
<a href=
"https://ci.appveyor.com/project/FeodorFitsner/appvyr-xunit-tests/build/1.0.25">
https://ci.appveyor.com/project/FeodorFitsner/appvyr-xunit-tests/bu...</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/359271112018-01-06T21:53:29Z2018-01-06T21:53:29Zappveyor.yml and assembly info patching<div><p>Is it possible to utilize environment variables here?</p>
<p>Or alternatively is there a suggestion for an assemblyinfo patcher to use instead?</p></div>ericnewton76tag:help.appveyor.com,2012-11-13:Comment/359271112018-01-08T21:41:06Z2018-01-08T21:41:06Zappveyor.yml and assembly info patching<div><p>As <a href="https://www.appveyor.com/docs/build-configuration/#assemblyinfo-patching">said in the documentation</a>: <em>You can use environment variables substitution in file name and version formats</em>.</p>
<p>Some more details: Variables <code>{version}</code>, <code>{build}</code>, <code>{branch}</code> are shortcuts implemented specifically to use with patching. Use them exactly as described (in <code>{}</code> curly brackets).</p>
<p>All <a href="https://www.appveyor.com/docs/environment-variables/">other environment variables</a> can be used too, but use them using standard environment variable notation -- <code>$(variable)</code>. Two other common environment variable notations (<code>%variable%</code> and <code>${variable}</code>) will work too.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/359271112018-01-10T19:26:43Z2018-01-10T19:26:43Zappveyor.yml and assembly info patching<div><p>Ah yes! I ended up finding that out after waking up the next morning.</p>
<p>During the Init phase, I end up creating an environment variable "APPVEYOR_BUILD_SEMVER" that can be used for the AssemblyInformationalInfo and for the actual BuildId</p></div>ericnewton76