Custom Packages not working in Latest Uipath Version

Hi All,
We had Custom packages developed by our clients and we were using them but recently we have UiPath studio Upgradation to 2024.10 earlier we had 2021.10.Since then custom packages stopped working so we informed same to our client and they worked on the issue and released new packages. However the packages are giving warning installing if we go ahead and install it its failing during compilation.
So please let me know if there are any configuration required while developing the Custom packages which should be compatible for latest UiPath version

@Aswini,

What’s the warnings you are getting while compiling?

@ashokkarale

i am getting the below while installing the package

@ashokkarale

Iam getting below error during compilation

@Aswini,

Expand the package dependencies and check the versions you have of the dependency - Microsoft.CodeAnalysis.CSharp

@ashokkarale

Hope this below details enough ?

@Aswini

So you have the same dependency in your custom package and System.Activities package.

What happens when you click on that Yes button on the popup?

@ashokkarale

The Package is getting installed after clicking on Yes but getting error if i try to run the bot during compilation get below error

@Aswini

If it was 21 it would have been in legacy initially and they would have migrated to windows

Now the issue you are having is a dependency different in your package and the system activity version that you are using

Please ask the team to use the same version of apckages to resolve the issue at package version and then use or use a system package version which is lower and that is not recommended

For migration help check here

Hope this helps

Cheers

Which package version you are referring to! Could you please elaborate on that please?

And FYI we have issue for Custom packages but not for custom activities

hello could anyone please provide some solution for the above issue ?

The status of dependencies in the tree is color-coded as follows:
Red - The dependency was not found.
Orange - A subpackage was not found.
Gray - The dependency is unresolved.
Faded Blue - The resolved version is higher than the requested version.
Strong Blue - There is an exact match between the requested version and the resolved version.

Based on this we can see that subpackage of Microsoft.CodeAnalysis.Scripting.Common is missing.
→ You need to resolve this missing subpackage issue first.

Cheers

@J0ska

Thank you so much for your response. Iam not the who implemented the custom packages but its done by our client team.

SO what i got to know from the developer is that he just upgraded the package UiPath. Workflow to make it compatible with Windows we had windows-legacy earlier

So once he installed that the below packages are getting downloaded automatically as per him

So Please help me understand that in order to make it compatible with windows do we have to upgrade UiPath. Workflow package or is there anything else that we need to work on ?

I never developed custom activities in Visual Studio so there I can’t help.

But I would recommend you to drill down the Microsoft.CodeAnalysis.Scripting.Common to find what subpackage is missing.
Then you could either contact the custom package developer to fix it or obtain the missing package via package manager.

Cheers

1 Like