Take your existing .NET framework applications and get them organized and ready to be included in a CI/CD pipeline by addressing package dependencies, configuration, and shared libraries, among other topics.
Adopting continuous integration and delivery for existing .NET applications is not as simple as setting up build and released definitions within VSTS or TFS. Preparations must be made within the applications themselves to support such a pipeline. In Preparing Existing .NET Applications for Continuous Delivery, you’ll discover those preparations, such as configuration management and dependency management. First, you’ll take some existing .NET applications, – including ASP.NET web apps (all flavors), WPF, WCF, and even console applications, and consider how each should be modified to fit within a CI/CD pipeline. Next, you’ll be re-arranging some things within the apps, which will mean some code modification and project structure changes. Lastly, you’ll create an efficient way to handle custom shared class libraries, and understand how to step into a real-world CI/CD pipeline that delivers a set of related applications across different environments in an automated fashion. Viewers should have a sense of what CI/CD is and have a basic knowledge of the overall structure of .NET applications. In-depth knowledge of .NET is not needed, but a basic familiarity is. When you’ve finished the course, you’ll be able to translate all that you've learned to your own apps. So, if you have existing applications that you are deploying manually and with much effort, this course is for you!
Course Overview Hi everyone, my name is Erik Dahl, and welcome to my course, Preparing Existing. NET Applications for Continuous Delivery. I'm a principal architect at RealPage. Continuous integration and delivery are great enablers to improving the ability of development teams to deliver value to your business and users, faster, and with higher quality than before. But getting a CIDC pipeline set up can involve a lot more than just setting up build and release definitions. In this course, we're going to explore some key considerations that should be handled in your applications to enable them to be included in a CICD pipeline. Some of the major topics that we'll cover include external package dependencies and their versions, configuration of your applications from local development to different environments and the safe-keeping of secrets, shared custom libraries that you have and how to best include them in your projects, and considerations for laying out different pre-production environments. By the end of this course, you'll know how best to handle package dependencies, how to handle configuration items for your application in easy-to-manage ways, how to publish and share your own packages across different applications and with different dependencies, and all of this will include content that works with. NET Framework and. NET Core, with some. NET Standard libraries that we'll explore. Before beginning the course, you should be familiar with basic. NET development of different application types, and maybe have just a little exposure to. NET Core and Standard. I hope you'll join me on this journey to learn about preparing your existing. NET applications for continuous delivery, here at Pluralsight.