Unable to load external dll
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-02-17 11:22 AM
When I try to load the HTMLAgilityPack dll. I'm getting the following error.
Could not execute code stage because exception thrown by code stage: Could not load file or assembly 'HtmlAgilityPack, Version=1.4.6.0, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' or one of its dependencies. The system cannot find the file specified.
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-02-17 03:13 PM
Hi VigneshSundar,
Try putting the dll inside the Blue Prism folder, and referencing it from the main page using the full path. I had this exact issue with acrobat.dll, and pasting it into the BP folder solved this issue for me.
Let us know if that works.
Felix
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
21-02-17 04:45 PM
We have tried placing the Blueprism folder(i.e. C:\Program Files\Blue Prism Limited\Blue Prism Automate\Interop.Domino.dll) as well but the result is same..
Internal : Could not execute code stage because exception thrown by code stage: Could not load file or assembly 'Interop.Domino, Version=1.2.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
22-02-17 02:14 PM
Yes moving the dll to blueprism folder worked for me
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
23-02-17 01:19 PM
We have even added the dll path (i.e. C:\Program Files\Blue Prism Limited\Blue Prism Automate\Interop.Domino.dll) under code options of initialize action's object properties(i.e. under external resources) and included the namespace under ""namespace imports"". But, We still see the dll dependency issue.
