Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Taprat is an powershell cmdlet for activating sharepoint features with the ability of specifiing properties. The idea is from Per Jacobsen's answer on SharePoint.StackExchange. The detailed description of the implementation can be found on my blog.

This cmdlet can be in two different ways: as a module (per session) or as a pssnapin.

Installation as a module

Download the dll from the install directory in Taprat. In PowerShell Go to the folder where you dropped the sp-lend-id.taprat.dll and import the module: Import-Module .\sp-lend-id.taprat.dll

Installation as a pssnapin

With a pssnapin you install it more or less permanently. To do so download the install/sp-lend-id.taprat.dll and in PowerShell go to the folder where it is. Then run these commands:

Set-Alias installutil $env:windir\Microsoft.NET\Framework64\v2.0.50727\installutil.exe
installutil .\sp-lend-id.taprat.dll

The script can be found in install directory. So you can simply drag-n-drop the install-pssnapin.ps1 into a powershell window (after your have navigated to the folder where sp-lend-id.taprat.dll is).

After the pssnapin is installed, you can add it to your session:

Add-PSSnapin sp-lend-id.taprat


When the cmdlet is loaded (after importing it as a module, or installing and adding it as pssnapin), just create properties as a hashtable:

$props = @{"Test" = "SPLENDID", "Title" = "Taprat" }

Copy your feature's guid. In the test project, it is: b5eef7d1-f46f-44d1-b53e-410f62032846 and then run:

Enable-SPFeatureWithProperties -Identity "b5eef7d1-f46f-44d1-b53e-410f62032846" -Url "http://dev" -Properties $props

The script (test.ps1) can be found in install folder as well.


This code is just a lab code for experimenting and learning purposes. Don’t use it in production environments unless you test it yourself. As Per Jacobsen pointed in his answer on Sharepoint StackExchange, the internal methods can vary in different releases and patches of SharePoint, which we can see here (Yaroslav’s code can’t be run anymore), and it can break your solution deployment.

You can’t perform that action at this time.