Thursday, May 25, 2006

Just released SharePoint SDKs; these look quite meaty -- The wss one weights in at nearly 34MB, compressed.

Windows SharePoint Services V3: SDK

This SDK contains conceptual overviews, programming tasks, samples, and references to guide you in developing solutions based on Microsoft® Windows® SharePoint® Services (version 3).
 
SharePoint Server 2007: SDK

The Microsoft Office SharePoint Server 2007 (Beta) SDK contains conceptual overviews, programming tasks, code samples, and references to guide you in developing solutions based on Microsoft® Office SharePoint® Server 2007.
 

I've also just installed the fresh Beta 2 releases on a virtual machine, so I'll be looking forward to porting my PowerShell SharePoint provider to v3...
posted on Wednesday, May 24, 2006 11:15:59 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0] Trackback
 Friday, May 12, 2006

Hmm, I just realised that RC1 and RC1 Refresh have different build numbers and are not binary compatible. Here's another drop built for rc1 refresh, 1.0.9567.0:

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

posted on Friday, May 12, 2006 12:44:05 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0] Trackback
 Wednesday, May 10, 2006

I've got the bones of a Compressed Folder (think zip files) provider lying around, and I was wondering if people would be interested to see a blog entry on how to put it together? I think I need a bit of a break from the SharePoint provider, so I'd be happy to write up a two-parter on how to get it up and running. Everyone seems obsessed with cmdlets; has anyone else got the psprovider bug, or is the learning curve too steep/documentation too confusing?

posted on Wednesday, May 10, 2006 11:22:48 AM (Eastern Standard Time, UTC-05:00)  #    Comments [3] Trackback
 Friday, April 28, 2006

Just some minor fixes, and the obvious API changes needed to be RC1 compatible. Source has been pushed the the MSH Community Extensions Workspace. For those of you who just want to play, you can get the latest binary at the bottom of this entry. Installation has changed slightly:

PS c:\temp> InstallUtil Nivot.PowerShell.SharePoint.dll
...
PS c:\temp> Add-PSSnapin Nivot.PowerShell.SharePoint
PS c:\temp> New-PSDrive wss SharePoint
http://mywss/
PS c:\temp> cd wss:
PS wss:\>

Apart from some minor refactoring, I've added some more actions to allow copy/move/delete between users/roles/groups and webs. Here's an example of how easy it is to define the operations for adding and removing users to a SPWeb using my generics-based provider model:

// add SPUser and place in Reader role by default
RegisterAdder<SPUser>(
    new Action<IStoreItem>(
        delegate(IStoreItem item) {
            SPUser user = (SPUser)item.NativeObject;
            NativeObject.Roles["Reader"].AddUser(user);
        }
    )
);

// remove SPUser
RegisterRemover<SPUser>(
    new Action<IStoreItem>(
        delegate(IStoreItem item) {
            SPUser user = (SPUser)item.NativeObject;
            NativeObject.Users.Remove(user.LoginName);
        }
    )
);

The above code allows the following to work:

   PS wss:\subweb> copy ..\!roles\contributor\username .

where . represents wss:\subweb, an SPWeb object.

Have fun!

Build RC1 Only, NOT RC1 Refresh -- for latest version see homepage 
Download: Nivot.PowerShell.SharePoint-0.51.zip (40.94 KB)

(edit: minor bug found -- v0.51 update)

posted on Friday, April 28, 2006 12:12:10 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0] Trackback
 Tuesday, April 25, 2006

Well, one sign that we're close to a release -- they've let the marketing monkeys out of their boxes for the day. What's the first stinky poop thrown from the cage? the name change: "powershell." I find all this kind of self-congratulatory naming very indulgent or something. I imagine the ultimate extension of this to be renaming a country to "WE ROCK."

I find it hard to believe that the richest company in the world can send a dozen highly paid marketeers into a room with their free soda and the best they can come up with is the "power" prefix. Anyhow, perhaps it fits in with the "powertoys" brand or something. Another thing that makes it seem a bad choice is that there are already several "powershell" products out there in the world. Not to mention "powerdiets," "powershoes," and no doubt several varieties of "power-pants."

Man, I'm spending too much time on this non-issue already. I'm starting to feel psychotic... go grab yerselves a new shell already.

http://www.microsoft.com/downloads/results.aspx?freetext=powershell&DisplayLang=en

 

posted on Tuesday, April 25, 2006 8:08:52 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0] Trackback
 Friday, April 21, 2006

I wish I could say I'm busy working on my SharePoint provider, but eh, no. I'm currently embroiled in the living hell that is house hunting: mortages, loans, notaries, agents and other such savagery. Why can't I just buy the friggin' thing on eBay? Oh yeah, just remembered why: you would pay $400,000; get hit by PayPal for $50,000; it would be the wrong colour; it would be late; the seller would insist on you paying via Western Union before shipping you a garden shed. etc etc.

 

posted on Friday, April 21, 2006 10:45:34 PM (Eastern Standard Time, UTC-05:00)  #    Comments [1] Trackback
 Sunday, April 09, 2006

...released to GotDotNet's MSH Community Extensions run by Monad MVP Blogger, Keith Hill.

posted on Sunday, April 09, 2006 12:20:16 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0] Trackback
 Wednesday, April 05, 2006

So, another drop for you today:

It now supports infinitely complex paths, and copy/move/delete:
 
e.g.
 
     # clear all alerts for the 'username' found in the contributor role
   remove-item wss:\site\subsite\!roles\contributor\username\!alerts\*
 
   # make the cross-site group 'crosssitegroup' part of the administrator role
   copy !groups\crosssitegroup  !roles\administrator\
 
   # upgrade perms for 'crosssitegroup' from reader to contributor
     move !roles\reader\crosssitegroup !roles\contributor
 
Of course, wildcards work too, so let loose!
 
pseudo containers (will tab complete, but not show up in get-childitems):
 
   !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
 
containers:
 
   user, group, role, list
 
leaf:
 
  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:
 
   installutil.exe nivot.monad.sharepoint.dll
   add-mshsnapin nivot.monad.sharepoint
   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

posted on Wednesday, April 05, 2006 11:31:49 AM (Eastern Standard Time, UTC-05:00)  #    Comments [0] Trackback