We have news that we want to share with you: as you might already be aware, the legacy .NET Framework 4.6.1 is no longer supported by Microsoft, which means that there won’t be any security patches released going forward. Therefore, after 2022.10, the Windows-legacy compatibility which is based on .NET Framework 4.6.1 will no longer be supported by UiPath Studio for new projects.
Why is this important?
Security and trust are two main factors that determine the usage of automations. Users are more inclined to use content that is updated with the latest product releases, and is secure. This is why we encourage you to take the necessary steps in this direction, as it will help both the users that have already downloaded your automations and the users that will discover your work as they access the Marketplace.
What does this mean?
From a Marketplace perspective, we need your help with the following aspects:
If you would like to publish automations on the Marketplace, please make sure your activities are compatible with .Net5 or later.
If you have already published activities on the Marketplace, please review them and migrate them to .Net5 or later versions. The Marketplace team has already started contacting each publisher to inform about this news, but proactivity is much appreciated.
To help with the migration of your activities, you can check this documentation article that offers an overview of how to migrate your custom .NET Framework activities to .NET 6 for use in projects with Windows and cross-platform compatibilities available starting with Studio 2021.10.6.
If you have questions or encounter any difficulties, please drop us a message and we will do our best to help.
Hello Alexandre,
I tried yesterday, for experimental reasons, exact the way described in the migration documentation. It works as expected and all packages are available:
System.Activities.Core.Presentation and System.Activities.Metadata
If I see it correctly this is a UiPath specific portation of the dotNET framework assembly (many thanks to the UiPath development team for this great work ). You can find it in your Studio installation, e.g. %USERPROFILE%\AppData\Local\Programs\UiPath\Studio. Not in a public repository, but available .
a tiny question to the marketplace: When we have converted our packages to the target platform net6.0, should we also change the runtime specification in the description? Is this a descriptive change or does a new version of the activity have to be uploaded then as well?
Yes, ideally you would need to update the information in that field, apart from updating the packages, but, when/if case, I do it on our end before publishing (like here ). It’s just a descriptive change in the Marketplace upload form, a new version is not required.
The activities of JShell and AutoIt are updated to .NET 6.
A lot of manual work and further impact than I thought. Especially if methods or properties from the .NET framework were used that are no longer available in .NET 6, I mean which generates an error or warning during compilation.
Thank you for migrating your activities to .Net6 and for your feedback related to this action. I know this was not an easy task, your effort is much appreciated.
The tutorial looks amazing, super useful information
One update on this topic: as you know, the custom activities published on the Marketplace can be discovered and used from the dedicated Studio feed.
Going forward, please note that in Studio 22.4 Windows target framework version, only the packages that are migrated to .Net 5 or higher will be displayed in the Marketplace feed. The packages that are not compatible with .Net 5 or higher will be present in Studio 22.4 Windows - Legacy version only.
Please feel free to reach out in case you have unclarities.
Kind Regards,
Andreea
I have a custom activity that I have migrated to .net6 with a dependency on UiPath.IntelligentOCR.Activities v6.6.0. It seems this package is not compatible with .net6.
Is there a place to keep track of Packages from the UiPath Internal Labs that need migrating?
I am currently trying to migrate all of my UiPath packages and I see I am going to be blocked by some of them due to some marketplace offerings still only having Windows - Legacy compatibility.
I did not say the package was blocked, I said it will block me completing migrations.
Check your own screenshots. It shows its not compatible with Windows Projects, you simply demonstrated you can search for it, not install it.
). You can find it in your Studio installation, e.g. %USERPROFILE%\AppData\Local\Programs\UiPath\Studio. Not in a public repository, but available 
.
). It’s just a descriptive change in the Marketplace upload form, a new version is not required.
Yoichi
Anil_G
jast1631
Gokul001
yedukondaluaregala
Jon_Smith
adi.mehare