Here's an example of AgentSVN documentation that doesn't match what I see --
https://www.zeusedit.com/agent/ide/vs/vs2008.html -- it mostly matches as far as I could go, but extra dialogs appear that are not mentioned and by Step 4 the who procedure is kinda off the rails because VS2022 or ...

Thank you for the link to the tutorial.

On my first try, I ignored the simplicity instruction and used these settings (mostly from another tutorial I'd found):
AgentSVN.png
Unfortunately, some things have changed and Step 4 locked up VS2022.

But, I might have done something wrong in step 4 ...

For the past 30 years we have been using M:\ as the folder to contain our projects. M: itself has always been mapped (either with SUBST or NET USE) to the actual location where the files currently being used were located. This made it easy for all projects to use the same path settings, etc. Our old ...

I just noticed that the log messages are not reporting the expected path. We use SUBST to 'create' an M: drive in the source folder where we will be working. This has always worked with other programs in the past. Apparently, AgentSVN (or maybe TortoiseSVN?) is being a little too smart and decoding ...

This is my first morning trying out AgentSVN x64 2.76 with VS2022 (and TortoiseSVN on Windows and Apache Subversion server on linux). Here's what I did:
Created a new, empty subversion repo on the server side
Started VS2022 and selected AgentSVN as my source control provider
Opened my solution ...