English | MP4 | AVC 1280×720 | AAC 44KHz 2ch | 2h 34m | 523 MB
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!
Table of Contents
Course Overview
1 Course Overview
What Does Your End State Look Like
2 Introduction and Overview
3 Definitions and Objectives
4 Challenges
5 Collaborate with IT
6 Overview of Demo Applications
7 Environments
8 Summary
Adopting a Strategy for Application Dependencies
9 Introduction and Overview
10 Repository Considerations
11 Folder Considerations
12 Apply Organization to Demo Projects
13 NuGet Considerations
14 NuGet – Allowed Versions
15 NuGet – Repository Path
16 NPM Version Handling
17 Version Control Considerations
18 Summary
Adopting a Strategy for Application Configuration
19 Introduction and Overview
20 Things to Consider
21 Demo – Locating Configuration Items
22 Assessing Demo Configuration Items
23 A Desired State Approach for Configuration
24 Demo – Overview and Defining Global Settings
25 NET Standard – Creating a Global Configuration Helper
26 NET Core – Applying Configuration Approach
27 NET Core – Using Dependency Injection with Configuration
28 NET Framework – Applying Configuration Approach
29 NET Framework – Allowing for Environment-Specific Overrides
30 Challenge and Summary
Adopting a Strategy for Custom Shared Libraries
31 Introduction and Overview
32 Package or Reference
33 NuGet Hosting Options
34 Package Publication Intro and VSTS NuGet Setup
35 Setting up Projects as Packages
36 Publishing First Packages with VSTS Build
37 Publishing Packages with Dependencies
38 NuGet Versioning
39 Demo of NuGetVersioning
40 NuGet Publishing Recommendations
41 Consuming Packages Demo
42 Shared Folder Executables Overview
43 Shared Folder Executables Demo
44 Final Build Readiness Check
45 Summary
Identifying Run-time Requirements for Deployment Environments
46 Introduction and Overview
47 Units of Deployment and Runtime Requirements
48 Environment Considerations
49 Final Readiness Checklist
50 Summary and Road Ahead
Resolve the captcha to access the links!