Greetings, I'm evaluating AgentSVN for use with PowerGUI Pro (quest.com) and PowerShell Studio 2012 (sapien.com) on Windows 7 Enterprise 64 boxes.
I've been using Tortoise but to get it's SCC working you've got to use version 1.3.5 from like 2004 and it doesn't appear to work on 64bit.
I just loaded AgentSVN on my Win7E64 laptop and pointed PowerGui Pro at it and it appears to be doing something. I've found the ASVN doc's to be quite dated.
I don't have any svn tools installed on this laptop so I didn't have a local copy...and like i said, it's doing something.
If we were to get ASVN would be free to use the latest, 64 bit version of Tortoise?
Also, the user guide says that you can use Tortosie as the SVN Project Manager...what exactly does that mean? Should I just type c:\the\whole\path\to\tortosie.dll????
MUCHO MUCHO MUCHO vagueness in what otherwise appears to be an OUTSTANDING product.
PowerShell
In fact...ASVN wouldnt work unless i put the path to an empty dir in Project manager. So like this:
SVN Project Manager: C:\peepeepoopoo
SVN Rep Dets
Folder: poopoo.peepee.net/svn/blah
Proto: HTTPS
Project Bonding Dets
Project: trunk
Directory: Any empty directory works
I totally wasn't expecting this behavior at all, I'm very puzzled by it.
SVN Project Manager: C:\peepeepoopoo
SVN Rep Dets
Folder: poopoo.peepee.net/svn/blah
Proto: HTTPS
Project Bonding Dets
Project: trunk
Directory: Any empty directory works
I totally wasn't expecting this behavior at all, I'm very puzzled by it.
This is true and it is not made any better by the fact that as from version 2.00 Agent SVN change dramatically. Some of the help might still be reflecting the older versions.I've found the ASVN doc's to be quite dated.
Because Agent SVN is MS-SCCI that means PowerGUI can see it and because it can see it, it will be doing something.I don't have any svn tools installed on this laptop so I didn't have a local copy...and like i said, it's doing something.
Now Agent SVN has never been tested with PowerGUI so you may still run into a few issues. If you do please report a bug.
Yes. AgentSVN uses the Subversion client to talk to the repository and not Tortoise.If we were to get ASVN would be free to use the latest, 64 bit version of Tortoise?
Generally you should be able to add any other tools you like. By default Agent SVN will only be using what is finds in it's own install folder.
Now this information I knew was in the helpd file, so I went looking for it. Turned out to be a little hard to findAlso, the user guide says that you can use Tortosie as the SVN Project Manager...what exactly does that mean?

Here is the bit I was looking for:
SVN Project Manager: This is the executable to be used as the project manager. If no executable is provide this dialog is displayed. For example if TortoiseSVN is installed the following command line could be used:
Code: Select all
"C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe" /command:repobrowser /path:"D:/projects/svnroots"
But this does mean that should you ever need to get back to this Agent SVN configuration dialog you will have to use the Windows Start menu.
Note: D:/projects/svnroots is the path to the repository.
Directory: Any empty directory works
Generally leaving the directory empty is the best option. I will update the help to reflect this point.
By leaving it empty the directory will then default to that of the project as passed in by the IDE which is generally correct.I totally wasn't expecting this behavior at all, I'm very puzzled by it.
Also I the directory is incorrectly specified then Agent SVN will not find the working copy resulting in many errors.
I have found working with Subversion has a habit of doing that to peopleMUCHO MUCHO MUCHO vagueness

Thank you.in what otherwise appears to be an OUTSTANDING product.
Cheers Jussi