Settings required to develop apps sharepoint 2013 on-premises

When developers don’t want to setup the domain Name in DNS, Visual Studio will modify the host file during debugging to skip the need of creating the Domain name in DNS for App development on Sharepoint 2013 development environment.

Pre-Req: Sharepoint 2013 root site collection created.

Step 1: Start App Management Service

$appManagementService = Get-SPServiceInstance | where {$_.TypeName -like “App Management Service”}

if($appManagementService.Status -ne “Online”) {
Write-Host “Starting App Management Service”
Start-SPServiceInstance $appManagementService | Out-Null
Write-Host “App Management Service was already started”

# wait for App Management Service to start”
while ($service.Status -ne “Online”) {
# delay 5 seconds then check to see if service has started sleep 5
$service = Get-SPServiceInstance | where {$_.TypeName -like “App Management Service”}

Step2: Start Subscription Settings Service

$subscriptionSettingsService = Get-SPServiceInstance | where {$_.TypeName -like “Microsoft SharePoint Foundation Subscription Settings Service”}

if($subscriptionSettingsService.Status -ne “Online”) {
Write-Host “Starting Subscription Settings Service”
Start-SPServiceInstance $subscriptionSettingsService | Out-Null
Write-Host “Subscription Settings Service was already started”

while ($service.Status -ne “Online”) {
# delay 5 seconds then check to see if service has started sleep 5
$service = Get-SPServiceInstance | where {$_.TypeName -like “Microsoft SharePoint Foundation Subscription Settings Service”}

Step 3: Create Service Application and Proxy for App Management Service

$appManagemetnServiceApplicationName = “App Management Service”
$appManagementServiceApplication = Get-SPServiceApplication | where {$_.Name -eq $appManagemetnServiceApplicationName}

# create an instance App Management Service Application and proxy if they do not exist
if($appManagementServiceApplication -eq $null) {
Write-Host “Creating App Management Service Application…”
$pool = Get-SPServiceApplicationPool “SharePoint Web Services Default”
$appManagementServiceDB= “Sharepoint_AppManagementServiceDB”
$appManagementServiceApplication = New-SPAppManagementServiceApplication `
-ApplicationPool $pool `
-Name $appManagemetnServiceApplicationName `
-DatabaseName $appManagementServiceDB

Write-Host “Creating App Management Service Application Proxy…”
$appManagementServicApplicationProxy = New-SPAppManagementServiceApplicationProxy `
-ServiceApplication $appManagementServiceApplication

Write-Host “App Management Service Application already exist…”

Step 4: Create Service Application and Proxy for Subscription Setting Service

$subscriptionSettingsServiceApplicationName = “Subscription Settings Service Application”
$subscriptionSettingsServiceApplication = Get-SPServiceApplication | where {$_.Name -eq $subscriptionSettingsServiceApplicationName}

# create an instance Subscription Service Application and proxy if they do not exist
if($subscriptionSettingsServiceApplication -eq $null) {
Write-Host “Creating Subscription Settings Service Application…”
$pool = Get-SPServiceApplicationPool “SharePoint Web Services Default”
$subscriptionSettingsServiceDB= “Sharepoint_SiteSubscriptionSettingsServiceDB”
$subscriptionSettingsServiceApplication = New-SPSubscriptionSettingsServiceApplication `
-ApplicationPool $pool `
-Name $subscriptionSettingsServiceApplicationName `
-DatabaseName $subscriptionSettingsServiceDB

Write-Host “Creating Subscription Settings Service Application Proxy…”
$subscriptionSettingsServicApplicationProxy = New-SPSubscriptionSettingsServiceApplicationProxy `
-ServiceApplication $subscriptionSettingsServiceApplication

Write-Host “Subscription Settings Service Application already exist…”

Step 5: Assign root domain name to configure URL used to access app webs

Set-SPAppDomain “” –confirm:$false

Step 6: Assign name to default tenant to configure URL used to access web apps

Set-SPAppSiteSubscriptionName -Name “app” -Confirm:$false

Leave a comment

Posted by on March 12, 2014 in Sharepoint


Sharepoint 2013 Search

Good Demo of SharePoint 2013 Search features

Leave a comment

Posted by on January 28, 2014 in Sharepoint


Dealing Sharepoint 2010 Performance Issues

Analysis, Debugging and Monitor

1) Use the SharePoint Dispose Checker Tool (SPDispose) to find memory leaks in custom software:

2) Enable the SharePoint developer dashboard and enable SQL Profiler to check SQL Server database problems

3) Get the Process Monitor tool for monitoring real-time file system, registry, and process/thread activity:

4) If page load is very slow, check if the ACL count is the problem, even when it’s well within the official limits:

5) Get to know SharePoint, its usage, and its response times by studying the IIS logs. One of the ways to do this is to use the free SharePoint Flavoured Weblog Reader (SFWR) tool:

6) Use the SharePoint Diagnostic Data Provider/Logging database to get more insight into your environment. Check out and

7) Use 3rd party analysis tools:,, (that includes Cardiolog),, or

8) Monitor performance counters that are relevant for SharePoint. The gallery post shows an overview of a set of relevant performance counters that have been established after careful research, and a small PowerShell script for reading them. Also see for a different perspective.

9) Get the SharePoint Administration Toolkit. It contains a load testing kit that can be employed to determine if an environment is able to handle the current load. It also contains SharePoint Diagnostic Studio 2010, a tool used by Microsoft personnel for troubleshooting. It’s able to capture lots of information about performance counters, ULS log files, and so on. See  for more information. If you find you’re having trouble that the ULS log files are empty, check out the following Wiki page:

10) Get PAL, a tool for troubleshooting performance troubles. See for more info. See for more info.

Optimization Considerations
1) The first authenticated user may experience a very poor response time. Consider warming up SharePoint. See for more info.

2) Enable ASP.NET profiling (, object cache (,  enable output cache.

3) Shrink the SharePoint content database transaction log files if they become too big or when it’s size increases abnormally:

4) Enable BLOB cache. See ,

5) Enable IIS compression. See

6) Configure list throttling. See

7) Use list indexes:

8) Limit the maximum upload file size

9) If you’re working with extremely large files, consider using Remote Blob Storage (RBS): and

10) Follow best practices when using the Content Query Web Part (CQWP):

11) Use a 3rd party performance optimizer tool for SharePoint (that uses compression, caching, and action prioritizing) such as Aptimizer:

Performance Testing for SharePoint

1) Do performance and stress testing, even if you’re already in trouble. It helps a lot to be able to simulate when a comparable environment gets into trouble. See , , , and

2) Use tools to test traffic on-the-fly:
Fiddler (, YSlow (,  and WireShark (


Plan and Study

1) Study other performance and capacity test results and recommendations:  and

2) Even if your environment is already up and running, do capacity planning. This way you can check if you’re crossing any important limits that might threaten performance. Check out and . Also check out, Maxer for SharePoint 2010 is a tool that checks for capacity boundaries in existing SharePoint farms.  Do remember that content database limits include remote BLOBs (if you use them) and that auditing has a great impact on capacity planning:

3) Study the set up of the database environment, which is crucial for the success of your SharePoint environment. The SharePoint 2010 Administrator’s Companion contains an excellent chapter about this:

Leave a comment

Posted by on November 27, 2013 in SqlServer


Useful links for SharePoint 2010 Branding


First add the CSS to the master page:

Starter Master Pages

Branding a Master Page

Fixed Width Layout

Dialog Boxes

Rounded Web Parts

Fixed Width

Sticky Footer



Search Center

My Sites

Rich Text Editor



Web Parts

Content Query Web Parts

Dataview Web Part


Article Series

Leave a comment

Posted by on October 4, 2012 in Sharepoint


Important SharePoint 2013 Features

Shredded Storage
In SharePoint 2010, if version history is enabled on a document library, each new version results in a new BLOB for that document. Second, I/O performance is problematic in SharePoint 2010. There’s an unnecessary file read that occurs when changes.At the highest level, what SharePoint 2013 shredded storage does is “chunk” or “page” the BLOB into numerous smaller shreds. So a single BLOB is now a construct made up of numerous shreds.So, for example, if you have versioning enabled and a user makes a change to a document, only changed shreds are added to the storage footprint of that document. Shreds that have not changed from the previous version are simply “associated” with both versions. Shredded storage also reduces the amount of information about a file that has to be retrieved by the web server from the content database, so I/O improves.

Business Connectivity Services
Support for OData Business Data Connectivity (BDC) connections, in addition to connections for WCF, SQL Server, and .NET assemblies. An event listener with an event subscriber on the SharePoint 2013, to enable SharePoint users to receive notifications of changes to the external system. Self-contained apps for SharePoint.

eDiscovery center is new site template, which creates a portal for managing cases—you can access cases to search, hold content, and export content.You can also now take the results of your eDiscovery search—including documents, wiki pages, Exchange email messages and tasks– and export them into a review tool.

Records management and compliance
Enhanced compliance simply by extending retention policies to SharePoint sites.

Business intelligence
New features in Excel for business intelligence (BI): In-Memory BI Engine (IMBI) for near-instant analysis of millions of rows of data; Power View Add-in for Excel, which offers visualizations, animations, and smart querying to enable users to visualize modeled data; decoupled PivotChart and PivotTable reports allowing for the creation of PivotChart reports without having to add a PivotTable report on the same page; and the ability to do trend analysis from cells in PivotTable reports that use OLAP data.

Microsoft made architectural changes in SharePoint Workflow.But if you want the SharePoint 2013 workflow platform, you need to install and configure Windows Azure Workflow to communicate with your 2013 farm.These new features include a visual workflow that uses a Visio 2013 Preview add-in, the ability to enable no-code web service calls from inside a workflow, new actions for the task process, the ability to start a workflow built on SharePoint 2010 from a workflow built on SharePoint 2013, and new workflow building blocks called Stage, Loop, and App Step.

Leave a comment

Posted by on September 28, 2012 in Sharepoint


Tools for sharepoint 2010

FAST Search Explorer Tool

Master Pages Developer Tool for SharePoint 2010

SharePoint Dispose Checker Tool

SharePoint Warmup Job utility

SharePoint 2010 Administration Toolkit

Leave a comment

Posted by on June 29, 2012 in Sharepoint



Tools to check fast index status

Run “Indexerinfo status” on fast crawl machine to check index count and non index counts

<documents size="32611257.000000" total="1" indexed="1" not_indexed="0"/>

“indexeradmin resetindex” can resume the indexer

Leave a comment

Posted by on June 26, 2012 in Sharepoint