Odd. I went back to using just the basics:
ps.AddCommand("Get-SvnRepository");
Collection output = ps.Invoke();
And now it's working. Initially, it told me it found the command in a
module that hadn't been imported yet. But now it's working. So that's a bit
weird.
On Tuesday, February 27,
I found one old message (from 2008) that asked for an API And I'm curious
if this is in consideration.
We're building some automation tools to free up some developer time for
managing SVN repositories in VisualSVN. I've been trying to use the
PowerShell cmdlets from within a Windows service
2 matches
Mail list logo
