This course will help get your code built when changes are committed, then get your IIS applications deployed using automated steps from VSTS or TFS! You'll see examples of this for ASP.NET Core and Framework sites as well as WCF apps.
Establishing solid build and release definitions for IIS-based .NET applications is a critical building block for true continuous delivery. In this course, Continuously Deliver IIS-based .NET Applications, you'll get into lots of the practical details that need to be addressed when delivering real applications via build and release definitions. First, you'll discover how .NET applications properly handle packages, shared library references, and configuration. Then, you'll try various flavors of ASP.NET applications and WCF services. All of these topics will be accomplished within Visual Studio Team Services (VSTS), and the same concepts would apply in various flavors of Team Foundation Server (TFS). Next, you'll learn about the build and release definitions within VSTS that will include most of the tasks and steps needed. Lastly, you'll take a close look at using PowerShell to perform custom activities when the predefined tasks don’t cover everything you need. By the end of this course, you'll not only be able to get your IIS applications deployed using automated steps from VSTS or TFS for ASP.NET Core and Framework sites but use Powershell for custom requirements as well.
Course Overview Hi everyone, my name is Erik Dahl, and welcome to my course: Continuously Deliver IIS-Based. NET Applications. I'm a principal architect at RealPage. Continuously deploying websites based on committed code changes can vastly simplify the overhead involved in introducing change for your web applications. In this course, we're going to explore some aspects of getting IIS applications built and deployed using continuous deployment techniques, and will be covering ASP. NET Core and Framework websites, along with IIS hosted WCF Services. Some of the major topics that we'll cover include: setting up build definitions that include multiple projects and result in published artifacts. Setting up release definitions that can deploy those artifacts as IIS websites and applications, with environment-specific settings. Triggering both the builds and the releases automatically, and using PowerShell to complete the automation process where canned options fall short. By the end of this course, you'll know how to set up build definitions that include multiple. NET projects, how to safeguard specific variables you want to keep secret during environment deployments, how to set up release definitions that can deploy all of your IIS- based projects, how to set up approval requirements for those deployments, and how to use PowerShell in deployment steps for some common certificate and IIS-related tasks. Before beginning the course, you should be familiar with some basic IIS concepts, and general concepts around ASP. NET web applications. I hope you'll join me on this journey to learn about automated IIS deployments, with the Continuously Deliver IIS-Based. NET Applications course, right here at Pluralsight.