Unexpected error has occurred during the library compilation process:
The assembly compilation returned the following errors:
- (1,2762): error CS0029: Cannot implicitly convert type ‘System.Activities.InArgument’ to ‘System.Activities.OutArgument’
Studio version : 23.10.3
Can anyone suggest me the possible reasons and solution for this error
Hey @thrinatha.boyathi1,
If you’re using VB.NETstrong text**** in a UiPath library and trying to assign an InArgument to an OutArgument, you’ll get a type mismatch error.
Correct way to do it:
OutputArg = New OutArgument(Of String)(Function(ctx) InputArg.Get(ctx))
Make sure:
- Replace
Stringwith your actual data type. - Use this inside the
Executemethod or anywhere you’re assigning arguments.
This lets you pass the value properly from input to output at runtime without a compilation error. Let me know if you need help adjusting it to your project.
1 Like
Welcome to the community
looks like one of the invoke workflow file arguments are not refreshed
try to check the same
cheers
Looks like in the workflow you have defined argument as in type but while calling that workflow you have defined argument as out type.
Please verify arguments under your invoke workflow if they match what is defined inside the workflow.
But same code is working fine till yesterday
Hi @Mir.Jasimuddin , Thanks for your response, but in my code I am not using any Library
Hi @Anil_G, Thanks for your response. Every Xaml is refreshed but still I am facing the same issue
Can you please provide a screenshot
As per the screenshot the issue is you are directly assigning an IN argument value to an OUT argument. Check the workflows you are using you can not directly assign.
can you check which xaml is throwing error as per logs many xamls are compiled…check which is not and specifically for argument type integer
cheers
Thanks @sonaliaggarwal47, @Anil_G, and @sonaliaggarwal47, the issue is resolved after making changes to the Argument name and scope
2 Likes
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.