A few months ago I wrote a series of articles on how to set up a release pipeline for dnx/dotnetcore projects with vsts targeting azure web apps.
This series would require you to use a few scripts to build and publish the website executing them using powershell tasks in the build definition.
You don’t need to do that anymore because two new extensions are available on the marketplace:
I’ve been able to replace most of my scripts using VSTS DNX Tasks
Here are my old articles as a reference
http://microsofttouch.fr/english/b/vince365/archive/2016/02/23/error-publishing-asp-net-5-core-websites-to-azure (replaced by the tasks)
http://microsofttouch.fr/english/b/vince365/archive/2016/03/03/controlled-update-of-sql-databases-schema-with-entity-framework-code-first-in-a-continous-delivry-process (still applies if you’re delivering entity framework models)
http://microsofttouch.fr/english/b/vince365/archive/2016/02/19/building-dnx-projects-using-home-installed-build-agent-tfs-vsts (still applies if you have your own agent)
http://microsofttouch.fr/english/b/vince365/archive/2016/03/01/units-tests-using-xunit-and-visual-studio-team-services-for-dnx-projects (still applies if you’re doing unit testing with xUnit)