I have faced the same exception while executing invoke code activity. I have resolved it by downgrading my uipath.system package to lower version from latest. Some how the latest system package is not able to compile the vb code and throwing exception related to syntax tree. Try and let me know. Thanks.
→ latest 2021.10.3 downgrade to 2021.10.2 it should work. for me this package version not giving me any error.
i have little bit confused i have tried with two version 2021.10.2 and 21.4.1 either one of the package version helped me to resolve the issue. try both versions and let me know. thanks.
Using uipath.system.activities 21.10.2
Method not found error; same error as with package version 21.10.3
Using uipath.system.activities 21.4.1
test.xaml: No compiled code to run
error BC30561: ‘DateFormat’ is ambiguous, imported from the namespaces or types ‘UiPath.Excel.Activities.Business, UiPath.Core.Activities, Microsoft.VisualBasic’. At line 2
I am sure this is related to the method which are trying to use both the Excel and other name spaces that made it ambiguous. Please remove the namespace if you added any new for this invoke code activity. Sure it will work. I think uipath.system.activity 21.4.1 resolve the syntax tree error.
Namespaces in the workflow (after a remove all unused):
Error message:
test2.xaml: No compiled code to run
error BC30561: ‘DateFormat’ is ambiguous, imported from the namespaces or types ‘UiPath.Core.Activities, Microsoft.VisualBasic’. At line 2
I’ve tried adding the Microsoft.VisualBasic namespace, but the same error occurs.
Hi @kirankumar.mahanthi1 ,
It doesnt work even if I downgrade my UiPath.System.Activities package.
Still populate same error “Method Not Found:Microsoft.CodeAnalysis.SyntaxTree”.
Can anyone help?
I found this had happened to me, and reverting the package back did fix it, unfortunately it broke another activity, so I had to revert it back again. In the same project I found another invoke method that was working. The only difference was the namespace system.security was imported on that workflow. Adding it and closing reopening the broken workflow seemed to fix it. Not sure if that was just a coincidence!
Can confirm that reverting the package version works, but if you’ve already built your project and now need to revert the package, especially a package like UiPath.System.Activities, it’s gonna cause missing activities and it’s a pain. Can’t UiPath fix this problem in their package?