Hi everyone,
there's something I really don't understand.
I'm currently using BPSExt-Signing-DocuSign extension
https://github.com/WEBCON-BPS/BPSExt-Signing-DocuSign/releases/tag/2022.1
When I clone the branch and build it, the build folder contains another (older) "System.ComponentModel.Annotations.dll" assembly than the release.
The reason for this is, that the plugin action CheckAllDocumentsStatus, which should be run in a cyclical action, fails due to an exception
Could not load file or assembly 'System.ComponentModel.Annotations.dll, Version=4.2.0.0, ...
The plugin uses the version 4.2.1.0, so I can understand why this fails. But I what don't understand is what artifact requires a 4.2.0.0 version.
I searched all .json, .config and .txt files in the directories WEBCON BPS Designer Studio, WEBCON BPS Portal and WEBCON BPS WorkFlow Service
The only hits for the filename I got were in the Portal directory. Which is of no importance as the cyclical action is run by the Workflow Service.
I also made sure that no other plugins in any content database used this file with another version. There was actually only this plugin which used the file
SELECT
[PLF_FullName]
,[PLF_Guid]
,[PLF_Extension]
,[PLF_PLPID]
FROM [DEV01_BPS_Content].[dbo].[PluginFiles]
where PLF_FullName like '%Annotation%'
I'm really lost here because I have no idea:
- Why an older version is requested,
- How I should know this in advance, up to now I added all assemblies to the plugin.zip which are not already "used" by the workflow service and bps portal.
- Get the assembly of the required version and assume that using another version will actually work. After all the plugin was not build with this version.
The other actions I tested so far worked fine, but than these are executed in the Portal process.
Best regards,
Daniel