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!

<#
.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

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

Use-CacheCluster
Get-AFCacheHostConfiguration -ComputerName YourServerName -CachePort "22233"

Use-CacheCluster
After starting a PowerShell session on a cache host, run this command without any parameters to use the connection settings that reside on the current machine. If you need to connect to a different cache cluster, use the Provider and ConnectionString parameters to specify the cache cluster explicitly.
http://msdn.microsoft.com/en-us/library/ff428183(v=azure.10).aspx

Get-AFCacheHostConfiguration
Cache port number of the cache host. The default cache port is 22233.
The output type is the type of the objects that the cmdlet emits.
http://msdn.microsoft.com/en-us/library/hh848875(v=azure.10).aspx

Cache Port
The cache port is used for transmitting data between the cache hosts and your cache-enabled application. The default is 22233.
Cluster Port
The cache hosts use the cluster port to communicate availability to each of their neighbors in the cluster. The default is 22234.
Arbitration Port
If a cache host fails, the arbitration port is used to make certain that the cache host is unavailable. The default is 22235.
Replication Port
The replication port is used to move data between hosts in the cache cluster. This supports features such as high availability and load balancing. The default is 22236.
HWM: The high watermark percentage of memory
When eviction should begin evicting objects that have not yet expired.
In other words: Removing objects from the cache that are not yet expired.
LWM: The low watermark percentage of memory
When eviction should begin evicting expired objects.
After reaching HWM, when eviction should stop evicting objects that have not yet expired.
In other words: Removing objects from the cache that are marked as expired and stop removing objects that are not marked as expired.
IsLeadHost
Not used in SharePoint

The purpose of this blogpost was to give you a quick answer on the question:
‘What is the Distributed Cache size on a specific server?’

For more information, please read this very detailed blogpost from Josh Gavant:
http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-2.aspx

Source:
http://technet.microsoft.com/en-us/library/jj219613.aspx
http://msdn.microsoft.com/en-us/library/ee790914(v=azure.10).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

Note: List items with unique permissions is sheduled and will be integrated in this script.

cls
Write-Host "********************************************************************"
Write-Host "| This script will check if there are list with unique permissions |"
Write-Host "********************************************************************"
Write-Host
Write-Host "Loading Microsoft.SharePoint.PowerShell..." -ForegroundColor Yellow
Write-Host

Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue

$siteURL = Read-Host "Please provide url of the SiteCollection"
$loglocation = Read-Host "Please provide path for the log file (hit ENTER to not store output)"
$site = Get-SPSite($siteURL)

Write-Host
if($loglocation -ne ""){
	start-transcript -path $loglocation
	Write-Host
}

Write-Host "--------------------------------------------------------------"

$counter = 0
Write-Host "The following lists and libraries have unique permissions `r`n (results marked in Red might have an 64K ACL impact):" -ForegroundColor Yellow
Write-Host

foreach($web in $site.AllWebs) {
	foreach($list in $web.Lists) {
		if($list.HasUniqueRoleAssignments -eq $true)
		{
			$counter = $counter + 1
			if($list.ItemCount > 1500){
				Write-Host $list.DefaultViewUrl "- ItemsCount:" $list.ItemCount -ForegroundColor Red "`r`n"
			}else{
				Write-Host $list.DefaultViewUrl "- ItemsCount:" $list.ItemCount "`r`n"
			}
		}else{
			#Write-Host $list.DefaultViewUrl -ForegroundColor Green	 "`r`n"	
		}
	}
}
Write-Host "--------------------------------------------------------------"

if($counter -lt 0){
	Write-Host $siteURL "has no lists or libraries with unique permissions!" -ForegroundColor Green
}else{
	Write-Host $siteURL "has $counter lists or libraries with unique permissions!"
}
Write-Host "--------------------------------------------------------------"

if($loglocation -ne ""){
	Stop-Transcript
}
Write-Host

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!

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

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!

Please keep in mind that this is based on the Technical Preview…

If you create your own app in SharePoint 2013, you can make use of the _spPageContextInfo object that is provided when your app is loaded.

for example:

//Get the relative URL for the current SPWeb
var urlWeb = _spPageContextInfo.webServerRelativeUrl;

The following screenshot show you the properties and their values for the spPageContextInfo object in my app:

hope it helps!

PS: The object already existed in SharePoint 2010:
http://blog.tedpattison.net/Lists/Posts/Post.aspx?ID=9