studio
latest
false
UiPath logo, featuring letters U and I in white

Studio User Guide

Last updated Feb 26, 2025

About the Windows - Legacy Compatibility

Studio 2021.10 brought support for .NET-based projects and introduced the concept of project compatibility based on robot type. In releases prior to 2021.10, all projects used the Windows - Legacy compatibility. Starting with Studio 2021.10 until Studio 2024.10, you had the option to create projects with the Windows and cross-platform compatibilities in addition to Windows - Legacy.

Automation Cloud users can choose between:

  • Studio LTS - Provides long-term stability with an annual release cycle.

  • Studio Continuous Release - Delivers frequent updates and new features while maintaining reliability.

To learn more, refer to the Product lifecycle support terms page.

The table below highlights the key differences between the two Studio versions:

Studio versionTarget audienceCloud connection requirementWindows - Legacy supportSupport modelRelease cycle

Studio LTS

Studio Year.10.Patch

E.g.: 2024.10.8

Enterprise users needing long-term support, stability, and Windows - Legacy support. Can be used for both on-premises and Automation Cloud/Automation Suite connections.

not available

available

Long Term Support (LTS)

24 months Mainstream support + 12 months Extended support.

Once a year.

Studio Continuous Release

Studio Year.0.Patch

E.g.: 2025.0.157

Enterprise users wanting frequent updates and new features while maintaining reliability. Can only be used with Automation Cloud connections.

available

not available

Continuous Release Support

Each release is supported until the next update.

Every two months.

Studio LTS will continue to allow opening and editing Windows - Legacy projects for the foreseeable future.

Studio Continuous Release no longer allows the creation or editing of Windows - Legacy projects.

The last Studio LTS that allows the creation of Windows - Legacy projects is Studio 2024.10. This option can be enabled through governance policies.

Benefits of converting Windows - Legacy projects to the Windows compatibility

The default compatibility for new projects is now Windows. Creating and editing projects with the Windows - Legacy compatibility is no longer supported, meaning that new features will only be available in projects with the Windows and cross-platform compatibilities.

Using the Windows or cross-platform compatibilities unlocks future innovations and prepares you for the UiPath Agentic Automation vision, featuring:

  • Robots that handle structured, rule-based tasks efficiently.
  • AI-Powered Agents that process unstructured data and make intelligent decisions.
  • Humans that validate and oversee critical automation workflows.
Agentic Automation enables you to automate more complex processes, leveraging AI-driven decision-making across enterprise systems.
Access new capabilities

Windows and cross-platform projects give you access to a next-generation capabilities which are not available in Windows - Legacy, including:

Enhanced performance and scalability

Windows and cross-platform projects:

  • Are compiled and provides significant performance improvements, reducing execution time for automations.
  • Are ideal for large-scale automation scenarios with high transaction volumes.
  • Feature modern memory management and Just-In-Time (JIT) compilation.
Enhanced security
  • .NET includes the latest encryption algorithms and security protocols to protect sensitive data.
  • Active maintenance ensures quick resolution of vulnerabilities, minimizing risks.
Reduced technical debt
  • Converting Windows-Legacy projects removes reliance on deprecated libraries and outdated technologies.
  • Future upgrades and enhancements will be easier and more cost-effective.
  • Modern workflows are easier to debug, scale, and adapt to evolving business needs.

How to convert Windows-Legacy projects to the Windows compatibility

Important: 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 Guides.

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 managed based on the following rules:
    • If the same version of the package exists in the configured package sources, the version used in the Windows - Legacy project is not changed.
    • If the same version of the package does not exist, the version used in the Windows - Legacy project is changed to the highest patch of the nearest version.
  • 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.

    Note: 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 new window is displayed.



  2. 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.
  3. 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.

Blueprint for converting Windows - Legacy projects

This step-by-step guide aims to help you to seamlessly transition your automations from Windows-Legacy to Windows.
  1. Inventory and assessment - Prepare a detailed inventory of all your Windows - Legacy projects and their dependencies:
    • List all projects, libraries, and dependencies.
    • Assess compatibility with the Windows (.NET) environment.
    • Identify components that need updates or replacements.
    Note: The NuGet Package Explorer application can be used to inspect .NET target frameworks.


  2. Proof of concept - Test the conversion process on a small subset of workflows:
    • Select a representative workflow that has a library added as a dependency.
    • Perform a pilot conversion to identify challenges and blockers.
    • Validate the result with tests.
    Tip:
    • Create a backup of the Windows - Legacy project and library.
    • Do not change the name of the project or library when migrating.
    • Migrate the library first and publish it. Don’t worry – the migrated version of the library cannot be used in Windows - Legacy projects.
  3. Scaling - Convert all projects and libraries systematically:
    • Migrate all libraries and publish them.
    • Migrate all projects.
  4. Validation and testing - Ensure the converted workflows perform as intended:
    • Perform testing.
    • Address errors or compatibility issues iteratively.
    • Test interactions with external systems and data sources.
  5. Production deployment - Transition the project to the production environment:
    • Deploy workflows to production.
    • Monitor for stability and performance issues.
    • Provide user training or updated documentation if necessary.
  6. Post-migration monitoring - Report migration issues to UiPath for future improvements:
    • Send feedback.
    • Share challenges or solutions with UiPath representatives.

Known issues

IssueSolution
Some expressions are incompatible with Windows projects and need to be manually changed to successfully convert a Windows - Legacy project to Windows.
{} to new Object() {}
new Object() {task_output.Id.ToString,task_action,now,I_comment } to new Object() {task_output.Id.ToString,task_action,now,I_comment }
Validation errors generated by other expressions that worked before the conversion. Cut the expression using the CTRL + X keyboard shortcut and paste it back in the activity field using CTRL + V.
In a For Each activity, naming the variable whose values you want to iterate as “expression” results in a compilation error. Refrain from naming the variable "expression".

BC36915: Cannot infer an element type because more than one type is possible. Specifying the type of the array might correct this error.

BC30512: Option Strict On disallows implicit conversions from 'Object()' to 'String()'. The selected value is incompatible with the property type.

BC36914: Cannot infer an element type, and Option Strict On does not allow 'Object' to be assumed. Specifying the type of the array might correct this error.

Modern programming languages enforce stricter type inference compared to older versions.

Cast the array or the element to the desired type, for example:

{} to new Object() {}

<object>.ToString()

CType(<element>, Object)

Encoding-sensitive operationsAdd System.Text.Encoding.RegisterProvider(System.Text.CodePagesEncodingProvider.Instance) using InvokeMethod.
“ (0x201C) vs. " (0x22) Replace all instances with " (0x22), which is the only valid quotation mark for string literals in modern .NET.
BC30311: Value of type 'SecureString' cannot be converted to 'CvString'. The selected value is incompatible with the property type.Remove and re-add the Computer Vision activity arguments.

BC31424: Type ‘System.Data.DataTable' in assembly ‘…’ has been forwarded to assembly 'System.Data.Common’ …

BC30652: Reference required to assembly ‘System.Collections’ … containing the type 'List(Of )'. Add one to your project.

BC30057: Too many arguments to 'Public Overloads Property SpecificContent As Dictionary(Of String, Object)'.
To fix these validation errors:
  • Navigate to the activity properties that contain the errors.
  • Remove the configuration (Cut or Ctrl + X).
  • Click outside the activity.
  • Add the configuration back (Paste or Ctrl + V).

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo White
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.