<?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 Maybe duplicating the dll in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76672#M29125</link>
    <description>Maybe duplicating the dll file so that it is also where your code wants it to be, and/or maybe adding the dll to the environment paths string in system settings?
Generally speaking, I think running the 64bit version of BP on a 64 bit windows OS sounds like the correct thing to do.</description>
    <pubDate>Mon, 22 May 2017 14:40:00 GMT</pubDate>
    <dc:creator>Denis__Dennehy</dc:creator>
    <dc:date>2017-05-22T14:40:00Z</dc:date>
    <item>
      <title>64 bit BP install with 32 bit VDI's</title>
      <link>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76669#M29122</link>
      <description>We currently have 3 developers using a 32 bit install of BP and our VDI's also have 32 bit BP installed.
Would there be any implications of me using a 64 bit install on my PC to develop? Could this cause any issues with our VDI's or other developers?

I am using version 5.0.23, in case you need to know.</description>
      <pubDate>Fri, 19 May 2017 14:00:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76669#M29122</guid>
      <dc:creator>JohnNicholson</dc:creator>
      <dc:date>2017-05-19T14:00:00Z</dc:date>
    </item>
    <item>
      <title>As with the installation of</title>
      <link>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76670#M29123</link>
      <description>As with the installation of any new version of Blue Prism (either a move from 32 to 64 bit, or an upgrade to a new version of the product), my advice would be the same.  Create a Sandbox installation environment (new database/environment) and regression test everything you have previously built.
I would expect the difference to be either non-existent or very minimal, with a slim chance that for some of your applications you may need to amend the Application Modeller mode (32/64/internal/external) for your interfaces to continue working.</description>
      <pubDate>Sat, 20 May 2017 16:05:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76670#M29123</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2017-05-20T16:05:00Z</dc:date>
    </item>
    <item>
      <title>Thanks, Denis. The main</title>
      <link>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76671#M29124</link>
      <description>Thanks, Denis. The main reason I want to move my machine to 64 bit is because I'm having issues with stepping through certain code stages that look for a .dll file in the blue prism installation folder. Because i'm running 32 bit on a 64 bit windows install it cannot find the .dll because it's looking in ""C:\Program Files"" rather than ""C:\Program Files (x86)"" where my install is. I've tried manually forcing BP to install into ""C:\Program Files"" but it always jumps back into the x86 folder. Besides installing the 64 bit version can you think of another work around for this?</description>
      <pubDate>Mon, 22 May 2017 13:32:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76671#M29124</guid>
      <dc:creator>JohnNicholson</dc:creator>
      <dc:date>2017-05-22T13:32:00Z</dc:date>
    </item>
    <item>
      <title>Maybe duplicating the dll</title>
      <link>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76672#M29125</link>
      <description>Maybe duplicating the dll file so that it is also where your code wants it to be, and/or maybe adding the dll to the environment paths string in system settings?
Generally speaking, I think running the 64bit version of BP on a 64 bit windows OS sounds like the correct thing to do.</description>
      <pubDate>Mon, 22 May 2017 14:40:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/64-bit-BP-install-with-32-bit-VDI-s/m-p/76672#M29125</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2017-05-22T14:40:00Z</dc:date>
    </item>
  </channel>
</rss>

