Published libraries, No compatible version with Windows - Legacy projects

Help Orchestrator
,
1

Hello,

I’m trying to make use of my own libraries in other projects, I manage to publish just fine and find my libraries in the Orchestrator Tenant tab of the Manage Package tab in Studio. However they just say, “No compatible versions with Windows - Legacy projects” when I try to implement them in a old project.

They are fine to import if I make a new project but I’m guessing that’s because they have been created on the same version of Studio.
I want to be able to work locally on libraries and functionality but I also need to work on a remote computer that has more sensitive data on it and so how can I ensure that my libraries can be used across PCs with different Studio editions etc.
I am very causious since I do not want to break anything.

2

I think your issue lies in that libraries created in Windows compatibility are not compatible in Windows (Legacy) processes. You would need to either create a second version of your library in Windows (Legacy) that you use in older processes, or upgrade your old processes to Windows.

1 Like
3

I did find some documentation and previous forum posts on this just after posting myself and you are absolutely right!
There seems to be some risks of migrating from Legacy to Windows depending on what packages and dependacies you have in your project since some were only built for legacy.
I’ll have to make do with creating a duplicate library for Legacy at this time it seems.

4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.