I would like to access a class library developed to do some processing against an external API. It seems like the most logical way to access its methods would be to utilize a Pega script component. While I am able to make a reference (via "Edit References") to the DLL, the script fails validation because it doesn't recognize the namespaces.
I am using Visual Studio 2015 with the Pega Studio Plug-in 8.0.1045
Write wrapper class by inheriting Component and then add the DLL in OpenSpan installation folder (C:\Program Files (x86)\OpenSpan\OpenSpan Plug-in for Microsoft Visual Studio 2015) and add to toolbox items in Pega Robotics Studio to use those methods in automation.
Thanks for the links. The second one had information that helped me resolve the problem. It turns out the simply changing the location of the DLL into the OpenSpan installation folder -- and then referencing it -- cleared up the problem where the namespaces were not recognized inside the Script component.
However, it doesn't make a lot of sense for OpenSpan to require this. It is not "clean" to require external DLLs to be put in the OpenSpan installation folder. We have several projects that will need to reference DLLs in this way. They are completely unrelated to each other, and we shouldn't have to clutter the installation folder on our development machines with DLLs that are not part of the core program. My two cents.
You should also be able to place them in %AppData%\OpenSpan\PublicAssemblies, however that doesn't solve the problem of keeping them in one place. I agree it would be nice to reference them from anywhere.