I apologize if this has surfaced before, but I noticed this error after the last uipath update. Should we wait for an REFramework update or is there something we need to do to fix it beforehand.
The error appears when we want to create a new REF project using Windows with C# options.
Hi @MikeStrike,
You can create a REF project with Windows Legacy and C#, after creation you can convert to Windows, in my case it was working.
Kind regards,
Robert
hey Robert,
Thanks for the reply.
Indeed, we have the option to convert to Windows after creating the project.
I was trying to create the awareness of the error when selecting this combination of options.
hopefully it will come with a future update on REF.
Cheers!
Hi @loginerror,
Do you know if there will be an REFramework update soon for this issue?
Thanks!
Robert
Hello!
We are planning on adding the REFramework configuration Windows C# in Studio 2023.4.
Until it becomes available, you can create a new project with this configuration starting from Legacy C# and convert it to Windows. After converting the project to Windows, one additional step is required: to remove the workflow GeneralTestCase from Tests folder, as it contains a dynamic Invoke Workflow (which is not supported in Windows projects).
Thank you, you have just solved a massive problem our team has had with publishing converted REFrameworks. So glad I found this!