Windows-legacy to Windows conversion: What about the Visual Studio made packages?

Help Studio
,
1

Hello Everyone!

So, this message came up after my Studio upgraded to 2022.10.1 that Windows-legacy components will no longer be supported in the next enterprise release.

I created a custom UiPath activity in C# using the UiPath Activity Creator in Visual Studio, and it seems like it’s considered as Windows-legacy.

How can I convert it to support .Net 5 or 6 (hence becoming Windows compatible in Studio), when the UiPath Activity Creator can only create .Net 4.6.1 packages?

Cheers

2

Follow the steps from here Using The Activity Creator

Even if at the beginning the Activity Creator 4.0 will show you .Net 4.6.1, in the end, it will be targeted to NET 6 Windows projects.

3

Hi,

Here you have documentation how to migrate project to .net5/6:

You can also check UiPath community activities repository from github. There were some projects migrated to newer .net:

5

Hello @Balint_Laszlo_Papp

Are these the custom packages?? If yes, it may not be migrated to .net6.

All uipath default packages supports windows as per my understanding.

Thanks

6

Yeah, it is a custom package. I built it for additional activities (non-UI, MS Office). Now I can’t get it work. The funny thing is that when I create a brand new project in VS2022 with UiPath Activity Creator, that’s not working either saying various dependency issues.

7

Those custom packages if you have created, then can you migrate that as well to Windows from Windows-legacy and check it once.

All the dependency packages should be compatible with .net6 to work in Windows.

Thanks

8

When I create a brand new project in VS2022 with UiPath Activity Creator, that’s not working either saying various dependency issues.

Response: It can be that some required dependencies are not found in the https://gallery.uipath.com/api/v3/index.json Marketplace feed

You can go to VS2022 → Tools → Package Manager Settings → Package Sources → Add new sources such as https://www.myget.org/F/workflow,https://www.myget.org/F/workflow/api/v3/index.json,https://uipath.pkgs.visualstudio.com/Public.Feeds/_packaging/Marketplace-Public/nuget/v2

image
image870×513 24 KB

image
image1752×1016 57.3 KB

The package sources will be stored at this location %USERPROFILE%\AppData\Roaming\NuGet\NuGet.Config

1 Like
9

I’ve managed to resolve this, thank you for your help.
Indeed, I needed to set up the uipath feed in the nuget package manager.
I created a new project, then I created the activities with the same name they had in the .Net 4.6.1 project.
After that, I copied all the codes/settings from the <project_name>.Activities\Activities and \Properties folders to the new package’s same folders.
I brought over the icons by copying the <project_name>.Activities.Design\Themes\Icons.xaml file.
I added a couple of COM dependencies back as well.

1 Like
10

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