VB or C# for new projects in 2024

Help Studio
,
1

Hi,

So what is the official recommendation for new projects in 2024?
Is it recommended to create the project using VB or C#?

What do you use?

What are the pros and cons of VB and C# respectively?

2

Hi,

I usually use VB, because UiPath supports VB for a long time and there are many knowledge. (C# is supported since 2020.10). In addition, VB has advantage regarding performance as the following document.

image
image1309×498 80.7 KB

However, recent new feature CodedAutomation supports only C#. If you are planning to use this feature actively, it might be good to use C# as project language from the view point of maintainability.

Regards,

2 Likes
3

I have been doing everything up till now in VB for UiPath related projects but for the latest one I went with C#. So far it looks like I need to write more lines of code to achieve the same result as in VB. Probably just a thing to get used to.

Just wondered if there is any news from UiPath and what they recommend going forward as I have heard that Microsoft maybe/already are? winding down with new features/upgrades for VB?

4

Evaluating by the language alone, Microsoft seems to recommend C# and C# engineer is more than VB. However, as far as I know, UiPath doesn’t say which is better in UiPath platform except the above C# limitation.
In my opinion, if you think stability, performance and much knowledge as important, VB is good. Or if you think future productivity etc. as important, C# may be better.

1 Like
5

Hi @atomic,

Microsoft have been shifting towards C# for quite a few years now. So has the community.

heres a thread from reddit from mid 2022
https://www.reddit.com/r/visualbasic/comments/w8o3ia/vbnet_end_of_life_pl_clarify/

if you read the Microsofts languages strategy, in the VB section they state they won’t be extending VB any further and refer explicitly to C#

If you compare the number of resources/posts/questions created past 2018, available for C# and VB, C# is clearly winning.

This is the reason why UiPath added support for C# and why some features are C#-only (like the ones mentioned above by @Yoichi).
While C# may still have some quirks in UiPath specifically, the direction is quite clear.

All new workflows I’m building are C# with a few legacy ones still in VB.
At the end of the day, if Microsoft are not planning on investing in VB any further, why should we :slight_smile:

3 Likes