<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>app-services on bramstoop.com</title>
    <link>https://www.bramstoop.com/tags/app-services/</link>
    <description>Recent content in app-services on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 22 Oct 2018 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/tags/app-services/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Disabling Sitecore config files in Azure App Service using Azure DevOps</title>
      <link>https://www.bramstoop.com/posts/2018/10/2018-10-22-disabling-sitecore-config-files-in-azure-app-service-using-azure-devops/</link>
      <pubDate>Mon, 22 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/10/2018-10-22-disabling-sitecore-config-files-in-azure-app-service-using-azure-devops/</guid>
      <description>BACK TO BLOG OVERVIEW
 Since we are keen on keeping the Sitecore scwdp packages OOTB as untouched as can be (as of our deployment strategy) we have two type of tasks in our release pipeline to disable/rename config files after deploying a vanilla package. Please keep in mind that, while using these tasks, we are always deploying to a staging slot with status &amp;lsquo;stopped&amp;rsquo;.
 While checking the script(s), note that you are able to write your own powershell scripts within the $commandBody variable: &amp;quot;$commandBody = @{ command = &amp;quot;powershell.</description>
    </item>
    
  </channel>
</rss>