Windows legacy to windows migration Issue

Help Studio
,
1

There is one automation which am migrating from windows legacy to (Vb, Windows ).

While doing the conversion we will get dependencies issue, unsupported activities etc., i have resolved all those issues in every other xaml except one.

This one .xaml is above 6 mb.

When i start working on fixing the dependencies inside that particular. Xaml, studio is either going to not responding or crashing.

Note i am doing this for a client, so there is no admin privileges available. Also i have tried with normal vdi and hds ones too still the same issue persists.

I appreciate any suggestions to effectively convert the pending one .xaml too.

2

@uipath
@ppr
@Vajrang
@mukeshkala
@Anil_G
@pradeep_ch

Any insights on this would help out greatly.!

3

Hi @Gautham_Pattabiraman ,

You can try this,

split the xaml, don’t open it directly, fix namespaces manually, and migrate logic incrementally. Trying to convert a 6+ MB xaml in one shot usually won’t work.

4

Hi,

It may be better to split the big xaml file into some small part in the legacy project, in advance. Then convert it to Windows project.

Regards,

5

This is too big. I would advise to modularize it in Legacy if you are able to and then migrate the smaller flows.

6

Try to modularise this xaml, also check may be there is a lot of imports, lot of revisions over time. Remove them, so only keep the used ones. This could be one reason your xaml is crashing..

And the other direction would be to:

create a new project with the same dependencies and copy over the XAML files one by one to see the point at which it will stop compiling.

7

Thanks for all your suggestions.

To overcome i started recreating from scratch after a while its again crashing.

One interesting idea/approach i have gotten.

While still keeping it in legacy, will remove the trouble makers particularly classic dictionary based activities with corresponding assign activity for dictionary manipulation.

Will be giving this one a whirl today and see how it goes.

Thanks people.

2 Likes
Forum Engagement Daily Reports
8

Everyone,

The spark worked. The project was stable enough to support the replacement of activities that ain’t supported in the windows project.

So i replaced all the activities that are needed while keeping it in legacy then took it to the folder where i had already kept the converted code.

Of course I agree with you all this is not the long time approach and guess what have updated the same in the scrum connect and we are planning to modularise the big .xaml post the conversion.

Just posting in the community after a while sparked with a solution for me.

Thanks to everyone who replied to my post as soon I had shared a query.

Happy automation.!

1 Like
9

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