<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: Problems with PATH containing location of external DLL's in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Problems-with-PATH-containing-location-of-external-DLL-s/m-p/50131#M5415</link>
    <description>Im also having the same issue, using the %PATH% does not work. Strangely the Blue Prism Object Studio is able to recognize class and namespace of the DLL but when we actually try to call it from the code stage it says it cannot find the assembly or reference.&lt;BR /&gt;&lt;BR /&gt;This is very important to us because we do not have elevated access to the automate.exe inside the program files.&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Eric Kim&lt;BR /&gt;RPA Developer&lt;BR /&gt;Huntington National Bank&lt;BR /&gt;America/New_York&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Fri, 13 Dec 2019 20:43:00 GMT</pubDate>
    <dc:creator>EricKim</dc:creator>
    <dc:date>2019-12-13T20:43:00Z</dc:date>
    <item>
      <title>Problems with PATH containing location of external DLL's</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Problems-with-PATH-containing-location-of-external-DLL-s/m-p/50129#M5413</link>
      <description>Following the below material, Blue Prism is not able to locate a DLL based on either a User or System Environment PATH.&amp;nbsp; (%PATH%)

&amp;nbsp;

&lt;A href="https://help.blueprism.com/Automation-Design/Studio/Code-Stages/1140179932/How-do-I-specify-External-References-for-third-party-code-DLLs.htm" target="test_blank"&gt;https://help.blueprism.com/Automation-Design/Studio/Code-Stages/1140179932/How-do-I-specify-External-References-for-third-party-code-DLLs.htm&lt;/A&gt;

&amp;nbsp;

The ONLY way I have been able to get Blue Prism to recognize and compile when using an external referenced DLL to do one of the following and/or a combination there of:

&amp;nbsp;

1).&amp;nbsp; Just put the DLL into the "Blue Prism Automate" folder.

&amp;nbsp; &amp;nbsp; &amp;nbsp;* This is not acceptable as in order to manage a DLL in that folder it is required to have elevated permissions to modify/change resources under Program Files.

&amp;nbsp;

2).&amp;nbsp; Use a combination of specifying an alternate storage location for the DLL (where the process has other access rights, but not elevated like administrator).. say "C:\MyDLL\MyDLL.dll".&amp;nbsp; &amp;nbsp;Then adding the full path of "C:\MyDLL\MyDLL.dll" to thee Code Options reference in the objects "Initialise" action.&amp;nbsp; &amp;nbsp;Then adding the DLL to the GAC using elevated permissions.

&amp;nbsp; &amp;nbsp; &amp;nbsp;* The action of adding the DLL to the GAC alone should allow one to NOT have to make hard coded path references to a DLL in the Code Options, just like how all of the .NET libraries are referenced.&amp;nbsp; The GAC contains the DLL... but without that, AND adding a hardcoded path to the DLL reference in Blue Prism along with an additional copy of the DLL somewhere in the file system path... it won't work.&amp;nbsp; Not acceptable.

&amp;nbsp;

Using a System Environment %PATH% addition to an alternate location with read/write access permissions to the process and/or account running the process should work and it doesn't.&amp;nbsp; Clearly something is not standard or working properly in Blue Prism.

&amp;nbsp;

Can this be addressed please?</description>
      <pubDate>Wed, 05 Dec 2018 00:08:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Problems-with-PATH-containing-location-of-external-DLL-s/m-p/50129#M5413</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-12-05T00:08:00Z</dc:date>
    </item>
    <item>
      <title>I would like to chime in on…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Problems-with-PATH-containing-location-of-external-DLL-s/m-p/50130#M5414</link>
      <description>I would like to chime in on this post and confirm I'm seeing same behavior which seems contradictory/incorrect from a standard deployment perspective.</description>
      <pubDate>Thu, 21 Mar 2019 23:02:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Problems-with-PATH-containing-location-of-external-DLL-s/m-p/50130#M5414</guid>
      <dc:creator>ScottPollard</dc:creator>
      <dc:date>2019-03-21T23:02:00Z</dc:date>
    </item>
    <item>
      <title>RE: Problems with PATH containing location of external DLL's</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Problems-with-PATH-containing-location-of-external-DLL-s/m-p/50131#M5415</link>
      <description>Im also having the same issue, using the %PATH% does not work. Strangely the Blue Prism Object Studio is able to recognize class and namespace of the DLL but when we actually try to call it from the code stage it says it cannot find the assembly or reference.&lt;BR /&gt;&lt;BR /&gt;This is very important to us because we do not have elevated access to the automate.exe inside the program files.&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Eric Kim&lt;BR /&gt;RPA Developer&lt;BR /&gt;Huntington National Bank&lt;BR /&gt;America/New_York&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Dec 2019 20:43:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Problems-with-PATH-containing-location-of-external-DLL-s/m-p/50131#M5415</guid>
      <dc:creator>EricKim</dc:creator>
      <dc:date>2019-12-13T20:43:00Z</dc:date>
    </item>
  </channel>
</rss>

