UiPath Studio

The UiPath Studio Guide

Deprecation of the Windows-Legacy Compatibility


Studio 2021.10 brought support for .NET-based projects and introduced the concept of project compatibility based on the target framework. In releases prior to 2021.10, all projects used .NET Framework 4.6.1, but since Studio 2021.10 you have had the option to create projects with the Windows - Legacy compatibility (.NET Framework 4.6.1) or with the Windows and cross-platform compatibilities based on .NET.

What deprecation means

The default compatibility for new projects is now Windows. While we continue to support the Windows - Legacy compatibility, new features and improvements will mostly be available only in projects with the Windows and cross-platform compatibilities.

For example, the following features introduced in Studio 2022.10 are not available in Windows - Legacy projects:

  • Support for creating global variables and constants in the Data Manager.
  • New design experience available for cross-platform projects and some activities in Windows projects.
  • The ability to customize the layout of activities generated from libraries.

Studio 2022.10 is the last release in which you can create new projects with the Windows - Legacy compatibility. Starting with Studio 2023.4, you will still be able to open and edit Windows - Legacy projects created in previous releases, but you will only be able to create new projects using the Windows and cross-platform compatibilities.



The execution of Windows - Legacy projects will continue to be supported in future releases.

Converting Windows-Legacy projects to the Windows compatibility

Studio comes with a built-in conversion tool that enables you to convert any Windows - Legacy project to Windows.

When you convert a project to Windows:

  • Project dependencies are replaced with the highest supported versions available in the configured package sources.
  • Dependencies for which no versions with the Windows compatibility are found are marked as unresolved and the version used in the Windows - Legacy project is displayed in the Project panel after the conversion.
    Most activity packages developed by UiPath and available on the Official feed support the Windows compatibility. For a complete list, see the Activities Guide.
  • All the activities and properties are preserved in the converted project.
  • Namespaces that are different in Windows - Legacy and Windows projects are updated.
  • Namespaces that are required in Windows projects are added and those used only in Windows - Legacy projects are removed.



Convert and republish Windows - Legacy libraries before you convert the processes where they are installed as dependencies.

To convert a legacy project to the Windows compatibility:

  1. Open the Windows - Legacy project in Studio and make sure you only open it in one Studio instance. A message is displayed at the top of the window.
  1. Select Convert to Windows in the message. Alternatively, right-click the project node in the Project panel and then select Convert to Windows. A new window is displayed.
  1. Select how to convert:
    • To create a copy of the current project using the Windows compatibility and keep the original Windows - Legacy project, select Create a new project. Enter the name, the location where to create, and optionally a description for the new project.
    • To update the existing project and convert it to the Windows compatibility, clear the Create a new project checkbox. The changes made to the project if you select this option cannot be undone.
  2. Click Convert.

If dependency issues cause unresolved activities after the conversion, a message displayed at the top of each such activity indicates that it is missing or it could not be loaded. The following information is available for each one: display name, activity namespace, activity properties and values. Click Replace to find an alternative and replace the missing or invalid activity. For more information, see Missing or Invalid Activities.

Updated 2 months ago

Deprecation of the Windows-Legacy Compatibility

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.