tag:help.appveyor.com,2012-11-13:/discussions/questions/849-writing-build-version-in-azure-websites-equivalent-to-deployment-labelAppVeyor: Discussion 2018-10-19T08:16:56Ztag:help.appveyor.com,2012-11-13:Comment/357376972015-01-09T19:54:46Z2015-01-09T19:54:46ZWriting build version in Azure Websites (equivalent to Deployment Label?)<div><p>Azure Websites are being published with Web Deploy which AFAIK
doesn't have a proper way of attaching some meta info. Maybe be
having <code>/version</code> endpoint is not a bad idea (or
injecting version number into HTML meta of home page?).</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/357376972015-01-09T22:53:14Z2015-01-09T22:53:14ZWriting build version in Azure Websites (equivalent to Deployment Label?)<div><p>Thanks! Thought that was the case wanted to make sure I wasn't
missing anything obvious. I went with <code>/version</code>
endpoints and it's working well.</p></div>toddtag:help.appveyor.com,2012-11-13:Comment/357376972015-10-28T22:17:43Z2015-10-28T22:17:43ZWriting build version in Azure Websites (equivalent to Deployment Label?)<div><p>I came across the same limitation when we moved our solution
from Azure cloud services to web apps, plus still have not found
any further verification if there is an OOTB solution.</p>
<p>One solution that I have implemented is to create a "version"
tag, which can then be assigned to the relevant Azure resource and
deployment slot. These tags can then be easily read via scripts or
whatever automation services you implement. From testing, the tags
do not get swapped with deployment slots, but that is easy enough
to automate, if desired.</p></div>Adam Webb