I've downloaded Rider to see what it's like, and I've opened an existing solution that is currently under source control (TFS/Azure DevOps server). In Rider's VCS->Enable Version Control Integration dialog, there wasn't an option for TFS/DevOps, but I figured that I had to install the "Azure DevOps" extension which added a "TFVC" entry to the list. Initially it complained that it couldn't find the TF command line, so I downloaded "Team Explorer Anywhere", and in Rider's Settings->Version Control->TFVC, I've selected the "tf.cmd" file for the "Classic TF command-line client" option. Is this correct so far?
Now, when I go into VCS->Enable Version Control Integration, and try to enable "TFVC", I see a couple of messages appear briefly ("Looking for TFVC workspaces", "Loading TFVC workspace"), followed by an error in the corner of the Rider window: "Couldn't create TFVC repository in C:\... - EULA not accepted". What am I doing wrong?
On a related note, as the solution is already under source control, does Rider utilise the existing *.vs**cc files and the various scc entries in project and solution files, or does Rider have its own equivalents of these? If so, will it screw up any of the Visual Studio source control integration settings if I was to subsequently open this solution in VS2019?