Starting with UiPath Studio version 2022.10, what happens to dependencies that lack Windows compatibility when they are converted in a project?
Starting with UiPath Studio version 2022.10, what happens to dependencies that lack Windows compatibility when they are converted in a project?
Starting with UiPath Studio version 2022.10, dependencies that lack Windows compatibility when converted in a project are marked as unresolved. This is done to ensure that users are aware of which dependencies need attention and potentially manual resolution to maintain the project's functionality.
Answer is C
Docs: https://docs.uipath.com/studio/standalone/2023.4/user-guide/about-the-windows-legacy-compatibility 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.
D. They are marked as unresolved.
From doc link in discussion, 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
1. https://skillrpa.com/index.php/2023/12/29/navigating-dependency-compatibility-in-uipath-studio-2022-10/#:~:text=With%20the%20release%20of%20UiPath%20Studio%20version%202022.10%2C%20a%20significant%20change%20was%20implemented%20to%20address%20the%20issue%20of%20incompatible%20dependencies.%20When%20converting%20a%20project%2C%20dependencies%20that%20are%20not%20compatible%20with%20Windows%20are%20now%20marked%20as%20unresolved. 2. https://docs.uipath.com/studio/standalone/2022.10/user-guide/about-the-windows-legacy-compatibility#:~:text=Dependencies%20for%20which%20no%20versions%20with%20the%20Windows%20compatibility%20are%20found%20are%20marked%20as%20unresolved%20and%20the%20version%20used%20in%20the%20Windows%20%2D%20Legacy%20project%20is%20displayed%20in%20the%20Project%20panel%20after%20the%20conversion.
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.