Question
Ameriprise Financial Inc
US
Last activity: 10 Jan 2024 11:00 EST
Pega Robot Studio V22 - Migration issue with c# class library
We have a solution in version 19.1.116 which has Pega and c# class library project in it. The reason for class library project is it refers some nuget dlls where we have custom code. Now when we are migrating this solution to v22 then I am not able to see c# project as a folder in Pega Project. Could you please guide how c# class library project can be added ?
Pegasystems Inc.
US
@ManishM5893 You should place any external DLLs into the %AppData%\Pegasystems\PublicAssemblies folder along with any of the DLLs that those DLLs require (that are not part of .Net or otherwise discoverable on your machine). You cannot load into the Pega Robotics IDE any other types of projects as you could with 19.1, as that was using Visual Studio 2015 as the IDE. You may continue to use Visual Studio 2015 for your C# projects, but you will need to compile them to use those DLLs within the Pega Robotics project by placing them in the %AppData%\Pegasystems\PublicAssemblies folder.
Ameriprise Financial Inc
US
@ThomasSasnett Thanks for your response! When you say placing them does it mean that we have to manually copy paste it and when it comes to runtime environment does it require again a manual placement on the machine too? Is there any way we can package these dlls in the Pega Project itself and once package is downloaded in runtime environment then these gets downloaded along with package.
I will give you some context and see if you can recommend a better way of doing it.
We are 2 teams which does legacy .net automations and one is Pega automations. There are few common functionalities which both team uses and we have nuget package for such functionalities. So in the current version of Pega V19 we used to add those nuget packages into our c# library project and reference c# project with Pega project under one solution. So what is the best way to access these common functionalities with v22 version. Please let me know if I need to raise an SR for this to go in detail as we need this info at the earliest to plan the migration for all our Pega BOTs.
Pegasystems Inc.
US
@ManishM5893 The best way to handle this is to build the DLLs in your current C# project on your development machine and place the output into the PublicAssemblies folder. The folder is important as it won't be able to properly add them to the project from anywhere else (technically it can also add them from the installation directory, but you'd need admin rights to place files there). When you reference those Dlls in your Pega Robotics project, they will be attached to the deployment package. You would need to do anything different than you do today in terms of how Runtime uses these Dlls. The placement of the Dlls is only necessary for Studio.
In 22.1, you would now use two IDEs: Pega's and Visual Studio. In 19.1, your Pega project could reference a .NET project and then build its Dlls and those of the .NET project together. In 22.1, we have created a new IDE strictly for Pega Robotics (to avoid a dependency on Visual Studio). You may still use Visual Studio for your .NET development. Your Pega project will need to reference the Dlls output by your .NET project rather than the project itself. Let me know if this makes sense.