It now supports infinitely complex paths, and copy/move/delete:

 

e.g.

 

     # clear all alerts for the 'username' found in the contributor role

 

 

     move !roles\reader\crosssitegroup !roles\contributor

 

Of course, wildcards work too, so let loose!

 

 

   !alerts, !groups, !roles, !lists, !users

 

When in the context of certain containers, only a subset of these will appear. For example, when in the user container, only !groups and !alerts are available

 

 

   user, group, role, list

 

 

  alert, listitem

 

I've implemented a handful of what I call "adders" and "removers" to allow basic copy/move/delete functionality between different types of compatible (and incompatible) paths. So, what do I mean by "incompatible?" For example, it is currently possible to do:

 

   move-item \!users\oisin \!roles\contributor\

 

So, what happens is the user oisin gets copied to the contributor role (ok) and then is removed from the source (not ok). In sharepoint terms, this makes oisin a contributor, and then removes him from the site users -- which also removes him from contributors :)

 

Since I plan to release the source when I get to a reasonable beta level, I don't want any dirty hacks. I'm taking the time to architect the copy/move/remove path rules properly, so as to give back a solid, reusable framework to the community.

 

Use with:

 

   new-drive <drivename> sharepoint <url>    ( e.g. new-drive wss: sharepoint http://localhost/ )

 

(old binary removed) - latest version always at:
http://www.codeplex.com/PSSharePoint