An item with the same key has already been added. Key: VisualBasicValue`1_1 error after upgrading to windows

[hari6 (Hari)]

Hi All Below is the error I am getting after upgrading the windows legacy process to windows. This is running completely fine in regular run but when I debug execution is not starting and throwing below error .
System.ArgumentException: An item with the same key has already been added. Key: VisualBasicValue1_1 at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer)
at UiPath.Executor.Tracking.ActivityIdsResolver.Register(WorkflowInfo workflowInfo)
at UiPath.Executor.Tracking.DebugTrackingParticipant.RegisterWorkflow(WorkflowInfo workflowInfo)
at UiPath.Executor.DebuggerPlugin.UiPath.Executor.IDebuggerPlugin.RegisterWorkflowTracking(WorkflowInfo workflowInfo)
at UiPath.Executor.Tracking.WorkflowTracking.RegisterWorkflowTracking(WorkflowInfo workflowInfo)
at UiPath.Executor.WorkflowRuntime.RegisterWorkflow(WorkflowInfo workflowInfo)
at UiPath.Executor.RobotRunner.InitWorkflowApplication()
at UiPath.Executor.RobotRunner.ExecuteJob()

[Yoichi]

Hi,

The following post will help you.

Troubleshooting Guide : Conversion from Windows-Legacy project to Windows project

This topic describes troubleshooting guide regarding conversion from Windows-Legacy project to Windows project as of Dec 2022. Hope this helps those who face these problems. 1 Quick Reference by Error Messages, Situation etc. Phase Error message / Situation Reference Open project foobar.xaml: Cannot create unknown type’{clr-Namespace:UiPath.foo.Activities;assembly=UiPath.bar.Activities}ActivityName’. 2.2 Missing Activities package OR 2.3 Missing activity Development Unable to set pro…

After Windows Conversion: "Unable to start execution: An item with the same key has already been added. Key: VisualBasicValue `1_1 "

SOLUTION! Took a while to dig into this, but I found that after converting a project from the Legacy framework to the Windows framework, it would not compile the Main.xaml any longer. Eventually, I found that the “VisualBasicValue1_1" key was being used for 2 different transitions. (In addition, "VisualBasicValue1_2” was also being used twice.) The new Windows framework did not like the fact that two transitions were being assigned the same key. (See below.) All I did to fix it was change one…

Regards,

[hari6 (Hari)]

@Yoichi Thank you it worked. Ideally we have to open the Main xaml in notepad and replace the VisualBasicValue 1_1 if there are multiple.

Thanks,
Harinath