<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>app-service-deploy on bramstoop.com</title>
    <link>https://www.bramstoop.com/categories/app-service-deploy/</link>
    <description>Recent content in app-service-deploy on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Sep 2019 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/categories/app-service-deploy/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Sitecore Identity server deployment: &#34;AspNetCoreRuntime extension not found&#34;</title>
      <link>https://www.bramstoop.com/posts/2019/09/2019-09-19-sitecore-identity-server-deployment/</link>
      <pubDate>Thu, 19 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/09/2019-09-19-sitecore-identity-server-deployment/</guid>
      <description>BACK TO BLOG OVERVIEW
 When you run in to the following ERROR while deploying your Sitecore XP solution, and in specific the Identity Server:
8:21:15 PM - Resource Microsoft.Web/sites/siteextensions &amp;lsquo;xxx/AspNetCoreRuntime&amp;rsquo; failed with message &amp;lsquo;{
&amp;ldquo;id&amp;rdquo;: &amp;ldquo;/subscriptions/xxx/resourcegroups/xxx/providers/Microsoft.Web/sites/xxx/siteextensions/AspNetCoreRuntime&amp;rdquo;,
&amp;ldquo;name&amp;rdquo;: &amp;ldquo;xxx/AspNetCoreRuntime&amp;rdquo;,
&amp;ldquo;type&amp;rdquo;: &amp;ldquo;Microsoft.Web/sites/siteextensions&amp;rdquo;,
&amp;ldquo;location&amp;rdquo;: &amp;ldquo;West Europe&amp;rdquo;,
&amp;ldquo;properties&amp;rdquo;: {
&amp;ldquo;id&amp;rdquo;: &amp;ldquo;AspNetCoreRuntime&amp;rdquo;,
&amp;ldquo;title&amp;rdquo;: null,
&amp;ldquo;type&amp;rdquo;: &amp;ldquo;Gallery&amp;rdquo;,
&amp;ldquo;summary&amp;rdquo;: null,
&amp;ldquo;description&amp;rdquo;: null,
&amp;ldquo;version&amp;rdquo;: null,
&amp;ldquo;extension_url&amp;rdquo;: null,
&amp;ldquo;project_url&amp;rdquo;: null,
&amp;ldquo;icon_url&amp;rdquo;: null,
&amp;ldquo;license_url&amp;rdquo;: null,
&amp;ldquo;feed_url&amp;rdquo;: null,
&amp;ldquo;authors&amp;rdquo;: null,</description>
    </item>
    
    <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>
    
    <item>
      <title>Sitecore Symposium 2018 - Must read takeaways!</title>
      <link>https://www.bramstoop.com/posts/2018/10/2018-10-16-sitecore-symposium-must-read-takeaways/</link>
      <pubDate>Tue, 16 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/10/2018-10-16-sitecore-symposium-must-read-takeaways/</guid>
      <description>BACK TO BLOG OVERVIEW
 &amp;ldquo;Returning from this year&amp;rsquo;s Sitecore Symposium in Orlando, I would like to share some improved/new insights that have come to me due to attending some great sessions. Some of this blog post will assume you are using a Sitecore on Azure PAAS solution. Most sessions I attended were related to continuous integration, continuous deployment, architectures, scaling, high availability and disaster recovery. The sessions from Bas Lijten, Dennis Weston and Rob Habraken inspired me most and therefore I will elaborate/reflect on most of their content.</description>
    </item>
    
    <item>
      <title>ETIMEDOUT issues on App Service Deploy task (TFS)</title>
      <link>https://www.bramstoop.com/posts/2018/04/2018-04-26-etimedout-app-service-deploy-task/</link>
      <pubDate>Thu, 26 Apr 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/04/2018-04-26-etimedout-app-service-deploy-task/</guid>
      <description>BACK TO BLOG OVERVIEW
  We experienced issues while uploading files to the slot of an App Service. We were using the Azure App Service Deploy task. We have approximately 10 of these task within our deployment process. Sometimes the tasks succeed, sometimes they fail. We do not see any algorithm in this behaviour.
We are using TFS on-premises, version: 16.122.27102.1
With system,debug on true we notice the following ERROR output:</description>
    </item>
    
  </channel>
</rss>