Hi All, We have different teams working on same repository in github. old team is using 23.10.3 version of studio and for new team they have 25.0.0 in which windows legacy is not there. Can they continue to use 25.0.0 version of studio because what happens when then pull the code from github since legacy is not there in new version of studio project is converting to Windows because of which all the dependencies everything is changing to Windows. Is it okay to use two different versions of studios on the same repo or should they use same studio version?
How you are using this version in production. It’s not yet released for Enterprise and shouldn’t be used.
It’s fine for non breaking changes like we have in 2025 - Windows Legacy not supported.
ideally you can use but again why are you building on legacy for new processes as it is being phased out
also it depends on the project dependencies first unless the version are so apart
cheers
It’s recommended to develop on the same version that your robots run on. There is some backwards compatibility, but it just prevents issues. Same for different versions between the team: it’s possible, but it will go smoother if everyone is on the same version. Patch matters a little less. So all 23.10.X for example.
Windows-legacy is deprecated and it’s time to start converting your processes over to windows!
Yes Anil, even we have same doubt but yeah again the old team is working from long time so they are using 23 version. Coming to our case we are not sure if we develop in 25 and we face any issues
23 version also shows a banner saying not to use legacy
if you develop in 25 you might not (again 25 is not the correct one I guess would be 24.10 which is latest lts) have issues…just make sure to keep the system packages and all packages which are compatible with 23 to not have any issues
but recommended is to use same
cheers
cheers
You will.
For starters once you compile the code into a nuget it won’t run on their 2023 unattended robots cause of the .NET version used, you’ll also end up in some GIT hell because of the new version of studio adding things to the project that the older version doesn’t recognize, this will make it really annoying to do things like pulls without committing those extra things, and if you commit them you mess up the 23 version sometimes.
This is not even mentioning the Windows-Legacy issue, which is not supported in the latest community version, which you seem to be referring to.
You need to downgrade your studio version to the 23 version to match theirs. Thats the only way forward here.