SharePoint Module 3.2 Hotfix 1 now available
A new hotfix package is available for version 3.2 of the TMCore SharePoint Module. This package addresses a small number of bugs and enhancements. The full change list can be found below.
Systems Affected
This hotfix should be applied to any installation of the TMCore SharePoint Module 3.2 downloaded before 20th August 2010. If you downloaded your copy of the software from our site on or after this date, the hotfix is included in the package and you do not need to apply it again.
To determine if your system is affected, check the File Version property of the assembly NetworkedPlanet.SharePoint in the GAC (browse to C:\Windows\ASSEMBLY, locate the NetworkedPlanet.SharePoint assembly, right-click and choose Properties. The File Version can be found on the Version tab above Description and Copyright). This hotfix updates the File Version of the NetworkedPlanet.SharePoint assembly to 2.2.1.0 - if the file version shown is greater than or equal to 2.2.1.0, then you do not need to apply this hotfix.
Upgrade Instructions
1. Download the hotfix 1 package for SharePoint 2007 or SharePoint 2010.
2. The package is provided in a compressed ZIP file. Unzip the package on a machine in the server farm.
3. Upgrade the NPSharePoint.wsp solution. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:
stsadm -o upgradesolution -name NPSharePoint.wsp -filename NPSharePoint.wsp -allowgacdeployment -allowcaspolicies -local
4. Upgrade the NPOfficeServer.wsp solution. Use the following STSADM command:
stsadm -o upgradesolution -name NPOfficeServer.wsp -filename NPOfficeServer.wsp -allowgacdeployment -allowcaspolicies -local
5. Restart IIS and Windows SharePoint Services Timer
Change Log
ENHANCEMENT: Stored procedures for OneHop and TwoHop Query Web Parts were updated toimprove concurrency. There was no change to the interfaces for these stored procedures.
ENHANCEMENT: An optional property can now be used to delay processing of the profilescraper. The property sets a sleep period in milliseconds between each profile changebeing processed.
BUGFIX: Reduced the amount of SharePOint ItemUpdated events that are fired when an itemis deleted which is associated to other SharePoint items.
ENHANCEMENT: Optimised code to ensure references to the NPCL schema are usingcached schema whenever needed.
BUGFIX: Associated Topic Field Control was disposing of an active Web object
ENHANCEMENT: The profile scraper has been optimised to avoid unnecessary lookups ofuser topics in order to pass these topic ids to any custom profile scraper plug-ins.
Using PowerShell To POST Data to Web3
Sometimes it is useful to be able to use PowerShell to manipulate a Web3 instance - either because you are scripting a set of batch operations or because you are just in PS at the time and it saves swapping contexts.
POSTing data to a REST service with PS is really easy, the only small wrinkle with Web3 is the need to authenticate with the server. Assuming you are using the default Windows Authentication setup for your Web3 server, the following set of commands should get the job done:
$wc=New-Object System.Net.WebClient
$cred=Get-Credential
$wc.Credentials=$cred
$wc.UploadString($URI, $CONTENT)
The Get-Credential cmdlet will pop-up a dialog prompting for your username and password - if anyone knows of a way to avoid that please let me know! If you need to load the content from a file, use the Get-Content cmdlet.
