C# Support Temporarily Removed in Studio 19.10

C# Support Temporarily Removed in Studio 19.10

We introduced the option to create C# projects in Studio 19.6, under the “Experimental” label, and since then we’ve been working hard to improve the reliability of our C# support. However, if you are using C#, you have likely noticed the quality is not yet good enough to remove the “Experimental” label.

Our upcoming 19.10 release is our annual Long-Term Support (LTS) Enterprise Release. We have an even higher quality bar on LTS releases, because customers rely on them long-term and we support them in the form of patches for an extended period of time (Enterprise SKU only).

Unfortunately, this means we cannot include experimental features in an LTS release - so we needed to temporarily remove C# support for the 19.10 release only. This means that in 19.10:

  • You will not see the option for C# when creating new projects
  • You will see an error message when opening an existing C# project

We want to reassure you this is temporary - we have heard loud and clear that you want the option to use C# in UiPath Studio projects. C# will be re-enabled in next month’s Community update. You can get support back sooner if you opt into our Preview channel (go to the Help tab and choose the “Preview” channel radio button on the right side).

If you need access to your project in the meantime, you can open it in Studio by opening the project.json file in a text editor (e.g. notepad) and changing the value of the “expressionLanguage” from “CSharp” to “VisualBasic”. This will enable you to open the project, but the project will not Build or Run successfully. At this point you can either convert the code in the project to Visual Basic or wait for C# support to return shortly.

Thank you for your patience and for helping us ensure a high quality LTS release for our customers. We apologize for the inconvenience.

19 Likes

Sad to see the missing c# option. Hope the team will get back stronger on flexible use of c# in UIPath.

Regards,
Karthik Byggari

5 Likes

What if our company has deadlines (to be certified) ? Did you think about that ?

2 Likes

I can’t even convert my project as It doesn’t show the values I want to edit but only, greyed: “Unregistered Expression Editor”…

1 Like

is there any way to downgrade ?

2 Likes

Not in case of Community Edition. Please stay tuned. This functionality should come back soon :wink:

4 Likes

We’ll be staying with the LTS for the year, and while this is unfortunate (I hate VB with a passion), it’s understandable. Let’s hope that C# is ready for a LTS version next time around. :slight_smile:

5 Likes

ETA when?

1 Like

When c# support is back and will be enabled???

3 Likes

Any updates on this?

2 Likes

This is work in progress and we will revert with an update when we have more we can share with you. Thanks for continuing to request this. We would love to hear more on how do you plan to roll this out in your CoEs and across teams, once it is available. Will you use both VB and C# inside the same team, switch to C# completely, split and have separate teams, split by process.

1 Like

@MirceaGrigore whenever C# is in LTS, the plan is to use it for any future projects from there onwards. Is there any word on the REF and Enhanced REF in C#? I think a lot of other COE teams would also greatly benefit from this.

Thank you all for your work on this! Hoping to hear about C# soon :slight_smile:

4 Likes

Yes. Our team is more proficient in C# than in VB, so we would prefer to even have everything on C#, if possible.

In my country, Bulgaria, for example, there are a lot of developers whose main language is C# and not that many with VB. Therefore, I am sure there are a lot of companies worldwide, which would prefer to use C# rather than VB.

3 Likes

Yes, because VB.Net its not popular language, here in Ukraine a bigger part of .net devs use c#, and its great language, give it back for us

2 Likes

Exactly as @olkuziv says. Here also nobody uses or knows VB and most people are proficient in either C# or Java.

Also, UiPath has a very similar design and approach to Visual Studio, so it feels comfortable for C# developers coming from Visual Studio. It would be perfect if it’s C# based, instead of VB based.

2 Likes

I would only use C# as a language. I’ve actually never met anyone who uses VB. C# is usually the 4th most popular programming, depending on the survey, and is only getting more developers as .NETcore becomes better. Especially with .NETCore 5 coming out at the end of 2020. Many people have Xamarin and ASP.Net projects that have a lot of code that could be used in a UiPath project. I doubt very many people have much VB code laying around. Furthermore, any Java developers would prefer to use C# as their syntax is nearly identical so you also have Java devs preferring C# to VB.

1 Like

@Pablito @AndrewHall Any updates on C# Support time lines? Havent seen anything in some time, curious to know if there was progress being made.
Cheers

Getting C# up to quality has turned out to be more difficult than we originally thought. We are still working on it, and are trying to get it added back by early summer, as you may have seen it’s unfortunately not in the 20.4 release which previewed yesterday.

1 Like

got it, thanks for the update! Looking forward to it.

1 Like

I need C# support for my projects. I don’t want to use old VB, I know and like C#.

You declared in November that next version will have C# support but when is that going to be? Or was it just a blunder?

1 Like