The issue is not fixed and UiPath is working on it. Kindly refer to my last comment:
Marketplace evaluator will allow you to publish activities written in the previous verison of .net untill future stable release. (This is what my understanding is. Also my activity is approved, published and live and it is written in .net4.6 only)
Hi, i am getting exactly the same error when using .NET Core 6. Any updates on this subject?
I’ve also tried:
include in my .net project the System.Activities dll and System.ComponentModel.Composition dll copied from the UiPath Studio folder (I’m using Community 2022.10.3). Result:
I can update my nuget package in UiPath Studio, but then it doesn’t compile:
include in my .net project the UiPath.Workflow.Runtime package (v6.0.3). Result:
I cannot update my nuget package in UiPath Studio:
“Cannot load assembly: …\docdigitizer.v1\18.104.22.1686231624\lib/net6.0-windows7.0/DocDigitizer.V1.dll : System.IO.FileNotFoundException: Could not load file or assembly ‘System.Activities, Version=22.214.171.124, Culture=neutral, PublicKeyToken=null’. The system cannot find the file specified.
File name: ‘System.Activities, Version=126.96.36.199, Culture=neutral, PublicKeyToken=null’
at UiPath.Studio.Plugin.Workflow.Services.AssemblyContainerBase.AddAssemblyInternal(Assembly assembly, String path)
at UiPath.Studio.Plugin.Workflow.Services.AssemblyContainerBase.<>c__DisplayClass15_0.b__0(Tuple`2 range) …”
include in my .net project the UiPath.Workflow.Runtime package (v6.0.3) and also the System.Activities dll and System.ComponentModel.Composition dll copied from the UiPath Studio folder. Same result as 2)
same as above but replacing the System.Activities dll of the UiPath Studio by System.Activities 6.0.3 dll. Result: UiPath Studio is broken.
My suggestion to fix this, is update UiPath Studio to work with System.Activities 6.0.3.
Hi, @Aeryn_Connerley I’m following your hint but same results (missing System.Activities, Version=188.8.131.52 while updating package in UiPath).
I changed UiPath.Workflow.Runtime to version 6.0.0 in my .net projet: “”.
However I think that UiPath.Workflow.Runtime nuget is available v6.0.3 only.
I don’t know much about UiPath, should I also change something in UiPath Studio? Could you guide me on that please?
Hi @hgk.sarmiento could you please describe your steps to overcome this issue?
@Hugo_Casqueiro Whether or not you’re using the Visual Studio UiPath Activity Creator Extension or creating the UiPath Activity project from scratch the way you edit dependencies / packages in .NET 6 Visual Studio projects is typically going to be by editing the .csproj file. In your project in Visual Studio select your .csproj file in the Solution Explorer (you may need to double click it to have it show up in the edit pane). In the original post of this thread that would be the dummyFLow csproj file.
Once you are in edit mode you will want to find the section with PackageReference. Find the UiPath.Workflow.Runtime package reference and for the version you should be able to change it to: 6.0.0-20220909-01 or wildcard it to 6.0.0-*. Save your project and it should refresh the package dependencies respective to that new version.
@Aeryn_Connerley Thank you for your kindness detailing all that.
Ok, I updated my .net project as you mentioned and now I can reference it in UiPath Studio (no more errors related with System.Activities, Version=184.108.40.206 ). However when I start debugging it throws this error:
Unexpected error has occurred during the library compilation process:
Unable to create activity builder for Main.xaml. Reason was ‘No matching constructor found on type ‘System.Activities.Activity’. You can use the Arguments or FactoryMethod directives to construct this type. No default constructor found for type ‘System.Activities.Activity’. You can use the Arguments or FactoryMethod directives to construct this type.’.
I retried it also with a new blank process from scratch, and without my reference it runs. When I install my reference (I’m doing it through Manage Packages) it throw’s the error above, even without any of my custom activities been used in the mainflow.