.png)
As a developer, I find it easier (and more productive) to code using C#.
This might be considered only as my opinion, but I think I’m not alone on this subject right? 
Is there a way of coding the activities using C# instead of VB?
Do the UiPath team consider adopting this language in the future?
Coding activities can be definitely done using C#: https://github.com/uipath
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.
It is not a Workflow Foundation Limitation. Since .Net 4.5 it is possible to use C# expressions in WWF as apoosed to VB.Net…
I would love to see UiPath use C# expressions.
https://blogs.msdn.microsoft.com/workflowteam/2016/07/20/building-c-expressions-support-and-intellisense-in-the-rehosted-workflow-designer/
Since UiPath is now .Net 4.6, is there a way to maybe get this activated?
This is a nice to have but we have other priorities so we’ll investigate when we have time.
Please have a look at this article
http://redmonk.com/sogrady/2016/02/19/language-rankings-1-16/
I agree that both languages make use of the .Net platform but their syntax is different.
I think it is safe to say that C# is more popular than VB. C# popularity is growing as apposed to VB declining
Maybe UiPath can have an option for the user to choose the language based on Roslyn compiler…
Will you integrate this functionality in 2018 maybe? It would mean building over .Net 4.5 minimum tho
From Studio software requirements:
.NET Framework
minimum: 4.5.2 recommended: 4.6.1
So that wouldn’t even be a change.
Building the actual studio over it. Not sure what your case is, but I haven’t a version of UiPath Studio that wasn’t built on top of .Net 4.0 so far.
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)