VB expressions on .NET 10

The .NET 10 runtime for VB expressions in Apps: which apps move to .NET 10, and what UiPath Apps Studio shows when an expression needs changes.

Apps compiles and runs VB expressions on .NET 10. Earlier versions of Apps used .NET 6. The upgrade affects how expressions are built and run in the browser, as described in Under the hood. It does not change how you design apps, and most expressions return the same results on both runtimes.

The upgrade applies automatically. You do not need to change any setting, and UiPath Apps Studio shows any expression that needs changes as a validation error.

Which runtime an app uses

An app runs on the runtime that was current when its expressions were last built. Published apps are not rebuilt automatically, so they keep working as they did before the upgrade.

App	Laufzeit
App published before the upgrade and not published again	.NET 6
App opened, previewed, or debugged in UiPath Apps Studio	.NET 10
App published, or published again, after the upgrade	.NET 10
App deployed through Solutions Management before the upgrade and not activated again	.NET 6
App deployed through Solutions Management, where activation rebuilds the app in Apps	.NET 10
App deployed through Solutions Management from a Studio Web solution package	The runtime the package was built with

Publishing a new version of an app moves it to .NET 10. For the steps, see Moving an app to .NET 10.

When an expression needs changes

When you open an app that was last built on .NET 6, UiPath Apps Studio checks its expressions against .NET 10. The check runs once for each app version. If an expression no longer compiles, UiPath Apps Studio displays the following message, with a Learn more link to this page:

Expressions now compile on .NET 10 instead of .NET 6. A few expressions are no longer valid and need changes.

The expressions that need changes are marked with errors, in the same way as other expression errors. The published version keeps running on .NET 6 until you fix the errors and publish a new version.

Some expressions still compile on .NET 10 but return a different result, so they are not marked with errors. For example, CDate("1/15/35") returns a date in 1935 on .NET 6 and in 2035 on .NET 10. The same applies to two-digit years from 30 to 49 converted with DateValue, Convert.ToDateTime, or DateTime.Parse. Four-digit years, or DateTime.ParseExact with a yyyy format, give the same result on both runtimes.

Apps in solutions

When a solution deployment activates an app, Apps rebuilds the app on .NET 10. If an expression no longer compiles, activation stops for that app and shows the following message:

This app was published when expressions compiled on .NET 6. Expressions now compile on .NET 10, and a few of them are no longer valid. Open the app in Studio, fix the expressions, publish a new version, and update the solution.

For more information about solutions, see Apps in Solutions Management.

Netzwerkanforderungen

The .NET 10 runtime downloads from the same UiPath content delivery network (CDN) as the .NET 6 runtime. If your firewall already allows Apps, no change is needed. For details, see Under the hood.