Coding activities can be definitely done using C#: UiPath · GitHub
Coding within the workflow (writing expressions in properties) can be done only in VB.NET. This is a Workflow Foundation limitation. We’re going to introduce the Code Activity and there you’ll have C# as an option.
A large number of developers want C# as their coding environment. It is not a question of whether they can code in VB as well or not. A large number of C# developers know C, F#, and some even know COBOL. That does not mean that those are the languages they want to use to code for UIPath Solutions. The choice is clear and it is C#.
UIPath should not be defensive about the current limitation and clearly state by when C# would be available as an option.
Microsoft Workflow Foundation is open source and hosted on Github. When UiPath forked an older version without C# support and don’t use the newest Microsoft version, then there is a chance that C# will be never available.
I agree with this idea. It only takes a quick google search to find out that VB.net is a dying language. Nobody uses it. Having a platform built on a dead language doesn’t seem like a good idea, so Invoke code (and most of the rest of uipath) should be in c#. I also think powershell should be an option in invoke code since I find the invoke powershell activity inadequate for more complex script writing (I’m not interested in writing external scripts with external tools, UiPath should handle it so everything can live natively in my workflow)