We've been using your task extension for quite some time now for all the steps that are necessary for the deployment of power platform solutions. We want to expand this now by starting to use the plugin registration extension task. I've noticed that is has been in preview for quite some time though. Can you give an estimate when it will get an official status?
Furthermore I've been looking for documentation about the plugin registration task but wasn't able to find any. I did read some of the issues on GitHub and some mention that a JSON configuration is necessary. How do you set this up? A remark I have about this though is that our plan is to only use the plugin registration task to update plugin dll's in a Dynamics solution after a Pull Request has been closed and a merge has been performed to a main or develop branch in a build and unit test pipeline. The idea behind this is to always have the latest (release) build of any plugins (in stead of adding it manually). The registration of plugin steps for instance will still be done using the plugin registration tool, and deployment adding the steps to a solution manually. If you only want to update the plugin dll's themselves, do you really need the json configuration?
Hope you can enlighten us in the usage of the plugin registration task.
Hi,
We've been using your task extension for quite some time now for all the steps that are necessary for the deployment of power platform solutions. We want to expand this now by starting to use the plugin registration extension task. I've noticed that is has been in preview for quite some time though. Can you give an estimate when it will get an official status?
Furthermore I've been looking for documentation about the plugin registration task but wasn't able to find any. I did read some of the issues on GitHub and some mention that a JSON configuration is necessary. How do you set this up? A remark I have about this though is that our plan is to only use the plugin registration task to update plugin dll's in a Dynamics solution after a Pull Request has been closed and a merge has been performed to a main or develop branch in a build and unit test pipeline. The idea behind this is to always have the latest (release) build of any plugins (in stead of adding it manually). The registration of plugin steps for instance will still be done using the plugin registration tool, and deployment adding the steps to a solution manually. If you only want to update the plugin dll's themselves, do you really need the json configuration?
Hope you can enlighten us in the usage of the plugin registration task.
With kind regards,
Johan Berghmans.