Custom Library not working in Windows Target Framework

[raghavbidani]

Hi,

We have a custom library where we make APIs call and extract the response in JSON format. It was working as expected in Legacy Framework but after converting it to Windows Framework (both project & Library) we are getting error from it. It is working fine if we run the library independently and also if we copy the xaml from library to project. But when we call the library from project we are getting the below error.

Please tell if are missing anything in this.

[raghavbidani]

@Palaniyappan @loginerror Any idea about this one?

[sai_gupta]

@raghavbidani

To resolve the error when calling a custom library from a project in UiPath Windows Framework, try re-importing the library and check for any compatibility issues with the new framework, ensuring that all dependencies are properly managed.

cheers…!

[Palaniyappan (Forum Leader)]

Make sure that the library is compatible with the version of UiPath that you are using.
You can check the compatibility of the library in the library’s NuGet package.

Check this thread for more discussion on this and a solution as well

Troubleshooting steps

Troubleshooting Guide : Conversion from Windows-Legacy project to Windows project

This topic describes troubleshooting guide regarding conversion from Windows-Legacy project to Windows project as of Dec 2022. Hope this helps those who face these problems. 1 Quick Reference by Error Messages, Situation etc. Phase Error message / Situation Reference Open project foobar.xaml: Cannot create unknown type’{clr-Namespace:UiPath.foo.Activities;assembly=UiPath.bar.Activities}ActivityName’. 2.2 Missing Activities package OR 2.3 Missing activity Development Unable to set pro…

Compilation Error in Process but not in Library: "Expression Activity type 'VisualBasicValue`1' requires compilation in order to run. Please ensure that the workflow has been compiled."

Hi, everyone. This issue is most likely due to 1 or more package misalignments. Specifically, the library is using UiPath.System.Activities 22.4.5, but the process that is using that library is on 22.10.3. Furthermore, our Studio is version 22.4. Still working on confirming that this is the issue, but it is more likely than not the cause. Word for the wise: keep your versions aligned! UPDATE: Confirmed that having the 22.10.3 version in the process interf…

Hope this helps

Cheers @raghavbidani