Home > Forum > Actions > Problem with SDK addition - A strongly-named assembly is required

Problem with SDK addition - A strongly-named assembly is required
2

Good morning,

After updating BPS to version 2023.1.3.240, we encountered an issue in our production environment.

The problem concerns an SDK add-in that enables sending XML data to MSMQ queues. We needed to update this add-in because, starting with version 2023, the methods were changed to asynchronous. The add-in relies on an external DLL file, Experimental.System.Messaging.

To include this DLL in the add-in, I had to sign it with a strong key. According to BPS, everything went smoothly—the package was implemented successfully, and the add-in functions correctly when the user proceeds through the path.
However, the issue arises when the document follows a path triggered by a global action.
In this case, the add-in generates the following error:

Could not load file or assembly 'Experimental.System.Messaging, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044) File name: 'Experimental.System.Messaging, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null'

It seems that, in this scenario, the add-in does not recognize that the DLL file is signed with a strong key. Has anyone encountered a similar issue?

MVP

Hi Łukasz,

based on your description I'm assuming that the assembly has not been signed before.

I would check:
- that the configuration defines the correct assembly for the action. The one in which all the actions/business rules etc. of this plug-in are defined.
- Create a new action using the current version. Maybe the XML contains outdated information.


Best regards,
Daniel

Did you know that with WEBCON you can automate virtually any process? Even baking cookies 🍪
 
Speaking of cookies: we use the ones that are essential for our website to function properly, as well as additional ones that help us customize our content to your preferences. If you don’t mind cookies, click Accept. If you want to learn more, explore settings.
Settings