SkyDrive Pro sync client is now available for Windows and can be downloaded here.

The SkyDrive Pro sync client ships with two components that are unselected by default. Microsoft does not recommend changing these default settings.

• Can be installed standalone and does not require any version of Office to be installed.
• This standalone client allows users of SharePoint 2013 and SharePoint Online in Office 365 to sync their personal SkyDrive Pro and any SharePoint 2013 or Office 365 team site document libraries to their local machine for access to important content on and offline.
• Size: 294.8 MB
• Supported OS:
  • Windows 7
  • Windows 8
  • Windows Server 2008 R2
  • Windows Server 2012
• It can also be installed side-by-side with previous versions of Office (2010, 2007).

https://play.spotify.com allows you to run spotify in your browser, meaning you can run the application on the Surface RT even if the spotify app is not available (yet?)

If you do not have the required cookie on your machine to participate in this beta, you are redirected to spotify.com.
The key here is to get the cookie or open the following site: http://www.spotifyweb.tk/

This evening I noticed that IE became not supported, it is possible to change the user agent string so that you are able to run spotify in your browser on the Surface RT.

Select the gear icon in the upper-right corner, select F12 developer tools > tools > Change user agent string to Chrome…

Hope it helps!

Very often I just want to know how many files with a specific extension are available in a SharePoint project.The following blogpost supported this goal.

<#
.SYNOPSIS 
Retrieves the amount of file based on a specific filter.

.DESCRIPTION
The Get-FileCountByFilter.ps1 script crawls a given directory and uses a user definied filter to count the files.

.PARAMETER Path
Specifies the path to the root directory to start searching and counting.

.PARAMETER Filter
Specifies the filter that is used to count only the files that apply to this filter.

.INPUTS
None. You cannot pipe objects to Get-FileCountByFilter.ps1.

.OUTPUTS
Sytem.Int32. Get-FileCountByFilter returns the number of results found.

.EXAMPLE
C:\PS> .\Get-FileCountByFilter.ps1 -StartDirectory c:\source\projects\
#>

[CmdletBinding()]
param (
	[Parameter(position=0, Mandatory=$true, ValueFromPipeline=$false, HelpMessage="Provide directory where all the result files are located.")]
	[string]$StartDirectory
	)
	
Get-ChildItem $StartDirectory -Recurse | ? {-not $_.PSIsContainer} | group Extension -NoElement | sort count -desc

Get-FileCountByFilter.ps1

Download content for ASP.NET, Office, SQL Server, Windows Azure, SharePoint Server and other Microsoft technologies in e-book formats. Reference, guide, and step-by-step information are all available. All the e-books are free. New books will be posted as they become available.

http://social.technet.microsoft.com/wiki/contents/articles/11608.e-book-gallery-for-microsoft-technologies.aspx

UPDATE 27/03/2013: If you simply want to upgrade your solution to SP2013, just dubbel click on the sln file on a dev server where SP2013 is installed.

UPDATE 21/03/2013: If you run this command you are able to start SharePoint 2010 solutions in Visual Studio 2012, as a side effect we are no longer allowed to create SharePoint 2013 solutions based on the templates.
Removing the added keys allows you to create SharePoint 2013 solutions, but than disables the SharePoint 2010 solution templates. Seems like we cannot have both…

If you want to import an existing SharePoint 2010 solution in Visual Studio 2012 you might encounter the following exception message…

This is due the fact that Visual Studio 2012 checks the “HKLM:\Software\Microsoft\Shared Tools\web server extensions\14.0\” registry if it contains the string value named “Location” before it allows you to continue.

If you run the following command inside your PowerShell window, the value will be set correctly.

Set-ItemProperty -Path "HKLM:\Software\Microsoft\Shared Tools\web server extensions\14.0\" -Name "Location" -Value "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\"

This location exists on my SharePoint 2013 development environment.
If you changed the location of the rootfolder during installation, please use the correct location here.

After you closed Visual Studio and restarted the application you should be able to continue.

Hope it helps!

Tom

Give it a look and try it out…It will make your life so much easier

Detailed guide:
http://www.camldesigner.com/2013/01/07/camldesigner-2013/

Available in the download section on the BIWUG site:
http://www.biwug.be/

KUDOS to Karine Bosch & Andy Van Steenbergen!

After you used the Run SPDisposeCheck on all assemblies in a specific directory with PowerShell script to validate all the assemblies in those packages. A report is created for each assembly found.

In order to visualize the results and communicate them towards the SharePoint team, you could use the following script that will open each SPDispose log file and combine them into 1 CSV file.

You can use Excel to open this csv file and create the pivot tables and diagrams you need in there.

cls
Write-Host "********************************************************************************************************************"
Write-Host "| This script will collect all the SPDisposeCheck result files and create one csv file with them for reporting	   |"
Write-Host "********************************************************************************************************************"
Write-Host

cls
$wspdir = Read-Host "Provide directory where all the result files are located"

#Retrieve the wsp files in this folder
$fileEntries = [IO.Directory]::GetFiles($wspdir,"*.txt");

$counter = 0;
$coll = @();

foreach($fileName in $fileEntries) 
{ 
	$content = Get-Content $fileName;
	$obj = new-object PSObject
	
	foreach($line in $content){
		#check if this line starts with ID: SPDisposeCheckID_
		if($line.StartsWith("ID: SPDisposeCheckID_")){
			$ID = $line.Replace("ID: SPDisposeCheckID_","");
			
			if($ID -eq 140){
				continue #false positive
			}
			
			$obj = new-object PSObject
			$obj | add-member -membertype NoteProperty  -name "Path" -value $fileName
			$obj | add-member -membertype NoteProperty  -name "SPDisposeCheckID" -value $ID -Force

			$counter = 0;
			$coll += $obj;
		}
		
		#Method information
		if($counter -eq 2){
			$line = $line.Remove(0,8) #remove Method: from string
			$obj | add-member -membertype NoteProperty  -name "Method" -value $line -Force
		}
		
		#Statement information
		if($counter -eq 3){
			$line = $line.Remove(0,11) #remove Statement: from string
			$obj | add-member -membertype NoteProperty  -name "Statement" -value $line -Force
		}
		
		#Notes information
		if($counter -eq 4){
			$line = $line.Remove(0,7) #remove Notes: from string
			$obj | add-member -membertype NoteProperty  -name "Notes" -value $line -Force
		}
		
		#More information
		if($counter -eq 4){
			$line = $line.Remove(0,18) #remove More information: from string
			$obj | add-member -membertype NoteProperty  -name "More information" -value $line -Force
		}
		
		$counter++
	}
	
	$coll | export-csv -Delimiter ';' "$wspdir\spdisposecheckrapport.csv" -notypeinformation
} 

The csv file named spdisposecheckrapport.csv will be stored in the same location as the result files are located.

Hope it helps!

/T

How awesome would it be, If you could:

1. Copy paste all the WSP’s that are installed in your farm into one directory
2. Run a PowerShell script to unpack the content:
   http://tomvangaever.be/blogv2/2012/12/unpack-wsp-packages-in-a-given-directory-by-powershell/
3. Have all the assemblies that are inside the WSP packages checked by SPDisposeCheck:
   http://tomvangaever.be/blogv2/2012/06/run-spdisposecheck-on-all-assemblies-in-a-specific-directory-with-powershell/
4. Create one report by using this script to aggregate all results:http://tomvangaever.be/blogv2/2012/12/an-aggregate-view-of-all-spdisposecheck-results-files-as-csv-file-via-powershell/

In order to extract the content of the WSP files by PowerShell, we need to use a built-in tool (extrac32.exe) that is available in your system32 directory.

The following script will un-pack all the WSP packages into their own directory.

cls
Write-Host "**************************************************************************************************"
Write-Host "| This script will unpack the WSP packages that it finds in a provided directory |"
Write-Host "**************************************************************************************************"
Write-Host

cls
$wspdir = Read-Host "Provide directory where all the wsp's are located"
$exportdir = "C:\Chorale\Audit-CRSE\Export-$((get-date).toString('yyyyMMdd-hhmmss'))\"

#Retrieve the wsp files in this folder and subfolders
$s = [system.IO.SearchOption]::AllDirectories
$fileEntries = [IO.Directory]::GetFiles($wspdir,"*.wsp",$s); 
foreach($fullFileName in $fileEntries) 
{ 
	$fileName = $(Get-Item $fullFileName).Name;
 	$dirName =  $fileName.Replace(".wsp","");
	$path = $exportdir + $dirName;
 	$dir = [IO.Directory]::CreateDirectory($path) 

	#uncab
	Write-Host "Export $fileName started" -ForegroundColor Yellow
	$destination = $path
	C:\Windows\System32\extrac32.exe $fullFileName /e /Y /L $destination
}

Once this operation is done you can use the following script to validate the assemblies: http://tomvangaever.be/blogv2/2012/06/run-spdisposecheck-on-all-assemblies-in-a-specific-directory-with-powershell/
Hope it helps!