I tried setting both CurrentCulture and CurrentUICulture in a process. When I did this, the process failed when process.xaml was to be run (reframework). This happens before any activities in process.xaml are executed. The error message doesn’t specify where the failure occurs, but it does mention that “1, 100, 59, 1200” is not a valid integer.
Through trial and error, I discovered that the error happens when UiPath tries to parse the xaml file in an activity. This is the first activity in process.xaml, which comes from a custom-made library. In the xaml file, there are several attributes formatted in this way, which I believe are screen coordinates indicating the area where the selector is located.
What likely happens is that the culture I set uses a comma as a decimal separator, which disrupts the parsing process.
I have never worked with changing CurrentCulture before, and I have concluded that I want to handle this differently, so currently, this isn’t an issue for me.
However, I am still curious for my own learning if I am doing something wrong when setting CurrentCulture, if it’s a bug in UiPath, or neither.