currently only with this package, the one’s that I install from other sources(downloading from GO & coping into Local folder, official, community) are working normally.
I’m getting the same behaviour with a custom package I’ve written. It’s working well in UiPath 2018.2.3 but shows the same type of error for 2018.3. How were you able to resolve this error?
Many thanks,
Thanks for your response! Do you mean the main UiPath project? Is this a difference between 2018.2 and 2018.3? I’m currently placing all the .dlls in the package.
Many thanks,
Indeed, I meant that the custom package should have the .dlls packaged.
The difference between 2018.2 and 2018.3 is the fact that 2018.3 introduced a strict dependency control. This means that only packages that are installed for that project are available as dependencies within that project.
Previously, any installed package was automatically a dependency for all projects in the future.
@loginerror, Thanks, that’s a clear explanation of how things are different between 2018.2 and 2018.3. I was missing System.Management.Automation, and adding that in fixed all!