Logo Barret Codes
  • Home
  • About
  • Engage With Me
  • Recent Posts
  • Posts
  • Dark Theme
    Light Theme Dark Theme System Theme
Logo Inverted Logo
  • Tags
  • .NET
  • .NET Aspire
  • Advent-of-Code-2021
  • Advent-of-Code-2022
  • Adventures-in-Net
  • AI
  • AI Builder
  • Ai-Art
  • Alexa
  • Api
  • Application-Insights
  • Approval-Flows
  • April-Dunham
  • Architecture
  • Ardalis
  • Asp-Net-Core
  • Aspire
  • Axug
  • Azure
  • Azure Back to School
  • Azure Cognitive Services
  • Azure Data Factory
  • Azure-App-Service
  • Azure-Devops
  • Azure-Functions
  • Balance
  • Big-Data
  • Bing-Maps
  • Bitly
  • Blazor
  • Blogging
  • BlueSky
  • Burnout
  • C#
  • C# Advent
  • C-Advent
  • Calendar
  • Canvas-App
  • Career
  • Change
  • Charity
  • Chatgpt
  • Cincydeliver
  • Civility
  • Class-Libraries
  • Cleveland C#
  • Code Reviews
  • Code-With-Ania-Kubow
  • Codementor
  • Cognitive-Services
  • Collections
  • Communication
  • Community
  • Conferences
  • Connectors
  • Content
  • Conversion
  • Copilot
  • Crm
  • Culture
  • Custom-Connector
  • Data-Types
  • Database
  • Datetime
  • Delay
  • Deployment
  • Deployment-Slots
  • Desktop
  • Development
  • Devops
  • Dotnet
  • Dotnetrocks
  • Dynamics
  • Ef-Core
  • ELT
  • Employment
  • Entity Framework
  • Equality
  • Error-Handling
  • Estimates
  • Ethics
  • ETL
  • Excel
  • Experience
  • Expressions
  • Extensions
  • Facebook
  • Facial-Recognition
  • Failure
  • Festive Tech
  • Festive-Tech-Calendar
  • Fired
  • Flow
  • Fluentmigrator
  • Forms
  • Function
  • Function Friday
  • Functions
  • Gatekeeping
  • GC 2.0
  • Giving
  • Gmail
  • Guidance-Counselor-2-0
  • Gulp
  • Hard-Drive
  • Hashtags
  • Hate
  • Hiring
  • HTTP
  • Hugo
  • Hybrid-Connector
  • Icymi
  • Ifttt
  • Iis
  • Image-Recognition
  • Images
  • Imposter-Syndrome
  • Inclusivity
  • Instagram
  • Interviewing
  • Javascript-Friends
  • Jira
  • Job-Search
  • Jobs
  • Json
  • Languages
  • Learning
  • Libraries
  • Life
  • Linkedin
  • Logging
  • Logic Apps
  • Love
  • Low-Code
  • Machine-Learning
  • Mastadon
  • Mentoring
  • Microsoft MVP
  • New-Job
  • Nodejs
  • Nosql
  • Nuget
  • Nz365guy
  • Object-Recognition
  • Ocr
  • OneDrive
  • Openai
  • Organizational-Skills
  • Outlook
  • Ownership
  • Ozcode
  • Pc
  • Podcasts
  • Pos
  • Power Automate
  • Power Automate Desktop
  • Power-Apps
  • Powershell
  • Privacy
  • Productivity
  • Racism
  • Razor
  • Recognition
  • Resharper
  • Responsibility
  • Retail
  • Rpa
  • Rss
  • Rss-Feed
  • Sass
  • Scheduled-Tasks
  • SciFiDevCon
  • Security
  • Security-Questions
  • Sentiment-Analysis
  • Service-Fabric
  • Sexism
  • Shorts
  • Slides
  • Smart Cherry
  • Smart-Home
  • Soft Skills
  • Sql
  • Ssl
  • Stackexchange
  • Stackoverflow
  • Startups
  • Stirtrek
  • Summit-Na
  • Surveillance
  • Task-Runner
  • Task-Runner-Explorer
  • Taylor-Desseyn
  • Teams
  • Tech
  • Templates
  • Text-Analytics
  • The-6-Figure-Developer
  • Time-Off
  • ToDo
  • Transition
  • Trello
  • Triggers
  • Troubleshooting
  • Try-Catch
  • Twitch
  • Twitter
  • Unplug
  • Uri
  • Video
  • Vision-Api
  • Vision-Service
  • Visual-Studio
  • Vsts
  • Web-Assembly
  • Website
  • Windows-10
  • Workflow
  • Xml
  • Xpath
  • YouTube
hero image
VSTS Deployment with Azure App Service Deployment Slots

Utilizing Azure Application Deployment Slots with the Visual Studio Team Services build and deployment system is quite simple. Set Up Deployment Slots The first step is to create your deployment slots for your application. You do this in your Azure Portal. Open the dashboard to your App Service application’s options. About halfway down the menu options that appear for your app you will see “Deployment slots”. Select this option. Click “Add Slot” and give your deployment slot a name. It also asks you to select whether or not to copy the existing configuration options from an existing slot. This will depend on your preferred deployment process. Some people let their deployment instance use all the same configuration options. I usually use the existing database connections, if any, but will alter any message queues, blob storage, table storage, and anything else that can trigger functionality on the back end, I point these to their respective testing versions so I don’t mess with production data unexpectedly. This is especially true for message queues, I feel. I want to be able to control the testing of the staging slot and not have it kick off unexpectedly if some production message gets through.

  • azure
  • deployment
  • deployment-slots
  • vsts
Saturday, November 11, 2017 | 6 minutes Read
Navigation
  • About
  • Engage With Me
  • Recent Posts
  • Posts
Contact me:
  • barretblake@live.com
  • barretb
  • Barret

Toha Theme Logo Toha
© 2024 Copyright Barret Blake.
Powered by Hugo Logo