I have created a package by using Activity Creator on Visual Studio 2023 and run it on latest UiPath 2023.4.0. But when i try to install the package on UiPath 2020.4.3 version, it gives me an error as mentioned below.
NU1202: Package xxxxx.Activities 1.0.5 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package xxxxx.Activities 1.0.5 supports: net60-windows7.0 (.NETFramework,Version=v6.0,Profile=windows7.0)
Latest activity creator uses .net5+ so…its not compatible…you need to either use old activity creator or change all the references to old packages as needed…
The references you would have used in the activity builder or creater are pertaining to .net5+ …you have to change them and whatever methods used from
Those classes are also to be removed or modified to old version
Hi @ceyda_eren
The error message you’re seeing indicates that the package you created using the Activity Creator in Visual Studio 2023 targets .NET Framework 6.0, which is not compatible with .NET Framework 4.6.1 that UiPath 2020.4.3 version uses.
To solve this problem, you have a few options:
Upgrade the UiPath version to a compatible one: Upgrade the UiPath version to a version that supports .NET Framework 6.0. This will allow you to use the package without any issues.
Repackage the activities to target .NET Framework 4.6.1: You can modify the package to target .NET Framework 4.6.1 instead of .NET Framework 6.0. This can be done by modifying the project settings in Visual Studio and recompiling the package. Once recompiled, the package should be compatible with UiPath 2020.4.3 version.
Create a new package that targets .NET Framework 4.6.1: You can create a new package using the Activity Creator that targets .NET Framework 4.6.1. This will ensure that the package is compatible with UiPath 2020.4.3 version.
I hope this helps! Let me know if you have any further questions.
we can create activities package which supports .net461 and .net6 from an activities package made by the latest activity creator.
The following document is for migration from .net461 to .net461 and net6 both support. However it helps you make it both support from .net6 activities package.