Continuing off of last week’s Package Deployer post I needed to add some extra functionality into our deployment that required the configuration of some steps that we were doing manually but now wanted to be done in a more automated fashion.
The task to accomplish this isn’t too hard and can be done relatively easily.
The first step involves decided “where” you want your code to execute. In my scenario, I wanted my code to Run after I had deployed all my customizations to the target tenant. In my example, I am deploying a base configuration after everything has been deployed. The “this.CrmSvc” is part of the runtime of the Package Deployer code which lets me access the current connection to Dynamics365.
//Implement the Default Configuration.
ValidateConfiguration config = new ValidateConfiguration(this.CrmSvc);