Microsoft has changed the way in which we must upload dependent assemblies that use our Plugins.
To do this, the first thing we must have installed on our computer is Power Platform CLI.
Subsequently, we will create a blank solution in our environment.
We will create a folder in which we want our Visual Studio project to be created.
We execute the console for Visual Studio developers and we will go to the folder that we generated in the previous step.
We will execute the command pac plugin init -ss true.
BE CAREFUL! This last one is important because for projects with dependent libraries it is NOT necessary to sign it.
We open the Project that has been generated.
We change the name of the Plugin1.cs file to the one we need and inside it we add our code.
We go to Manage nuget packages and add the dependent library we need. In this case we will add the DocuSign.eSign.dll library.
We compile the project.
When compiled, a nuget package will be generated in bin/debug.
Finally, we will deploy the nuget package generated in Plugin Registration Tool.
The following window will open in which we must choose the nuget package we generated in the previous step and the blank solution we generated in the first step.
Once the package is uploaded, we create the corresponding steps.
To conclude, we have detailed the process for uploading dependent assemblies to PRT with Power Platform CLI and Visual Studio. From creating a blank solution to deploying the generated nuget package, each step is essential to ensure the correct functioning of our plugins with dependent libraries.
Remember to have Power Platform CLI installed, create and configure the Visual Studio project, add the necessary libraries, compile the project and finally deploy the package in Plugin Registration Tool.
We hope you found this guide useful. If you follow these steps, you will be able to integrate and deploy your plugins efficiently. Good luck with your projects!
About the Author: Bárbara Jurado
