Migration Legacy to Windows - System.ComponentModel.TypeConverter, Version=8.0.0.0 error

Help Studio
1

Hi,

Getting the error when migrating Legacy to Windows version, how can we resolve this?

BC30652: Reference required to assembly ‘System.ComponentModel.TypeConverter, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ containing the type ‘MarshalByValueComponent’. Add one to your project.

The strangest thing is that this happens only for variables of type dataRow, which are being used in other files inside the project which are not throwing the same error. I tried what was suggested in another post from 2024 but it did not work.

Regards

2

Hi, @Testing360 Go to .nuget and rename the Packages folder to something like Packages_old and Reopen your UiPath project. This will redownload missing or corrupted packages again

In UiPath Studio, go to Project > Manage Packages, and make sure all essential packages like UiPath.System.Activities are updated properly and then rebuild your project

Also check DataRow variable types are consistently declared as System.Data.DataRow.

3

@Testing360

If its happening only in one xaml..try to recreate it as new or delete those variables and recreate

Cheers

4

Hi @Testing360

What versions of Studio and activity packages are being used?

Have you already tried updating the activity packages to their latest version?

5

Hi Arjun, I have done these steps that you suggested but sadly it did not work.

6

Hi, version 2024.10.1

I had already updated before the packages to the latest version and it did not fix the issue.

7

Whole file is too big to recreate. I tried deleting variables and recreating the sections throwing the errors but did not work.

8

One thing I would suggest to start is to update Studio to the latest patch version of your current LTS branch, which would be 24.10.16:

There is a big time gap between them, and it is likely that the issue was already addressed :crossed_fingers:

24.10.16 - Release date: 3 September 2025
24.10.1 - Release date: 1 July 2024

Other than this, it would help if you could give as much context as you can about your process. Knowing all the dependencies that are used in your project would be a minimum information for us to look into this further.

Having a small, new legacy project sample zip that you know breaks after the conversion would be ideal.

9

For compatibility issues between Legacy and Windows project I follow below guide.

Step 1: Prepare Your Files
Original.xaml: This is the old XAML file from your legacy project.
new_Original.xaml: Make an exact copy of Original.xaml. This will become the new XAML file for your Windows project.

Step 2: Analyze Activities in the Legacy Project
Open the legacy project.
Review the activities used in Original.xaml (e.g., Click activity, Type Into, etc.).

Step 3: Set Up a Test XAML in the New Project
Open the new project (Windows).
Add a test XAML file.
In this test file:
Add all the activities that were present in the legacy project’s XAML file.
You do not need to configure selectors or variables —just add the activities (single acitivity for each type). Do not miss any activity type otherwise it wont work.
Add all required arguments, ensuring the name and direction match those in the old XAML file.
Save and close the test XAML file.

Step 4: Merge Content Using Notepad++
Open both the copy of the old file (new_Original.xaml) and the test file in Notepad++.
In the test file, locate the section after x:Class=“xaml_file_here” in first line only.
Copy all content after this (first line only) from the test file.
Paste this content into the same location (replacing old content) in the copy of the old file (new_Original.xaml), replacing the corresponding section.

image

You might need to remove

  <mva:VisualBasic.Settings>
    <x:Null />
  </mva:VisualBasic.Settings>

from new copy file.

Declaimer: I used LLM to format my guide.

If you still face issue then if possible upload your Legacy workflow here for further troubleshooting

10

Unfortunately this didn’t solve the problem. I tried converting legacy to windows using the LTS version of studio and I still have the same issue. :frowning:

image
image942×423 22.3 KB

Also, this error is super strange because it is happening on a very basic data type, which is Datatable. And you can see from the screenshot that it is not even properly recognizing the variable type. Despite being declared an argument of type Datatable, UiPath studio is interpreting the variable as a string for some reason.