Last week, we already learn how to set up Azure DevOps Pipeline for Web Resources. And this week, we will learn how to set up the pipeline, but for the Plugin (backend customization). And the interesting part, we also will implement the Plugin Package (or plugin-dependent assembly). What we will accomplish will be like the diagram
It is frequently valuable to include another assembly or a resource file within a plug-in. For example, you may want to use Newtonsoft.Json.dll or another assembly. You may want to access a list of localized strings.
DevOps is dynamic and depends on Organization/people’s perspective on how to run it. For me, the “truth” source to be considered when deploying and publishing customizations for Plugin or WebResources is the code itself