SharePoint slow to start up after application pool recycled

After deploy solution through visual studio the application pool will be recycled.
Then it is painful slow to start the first page.

There are a few articles talking about this,
http://blog.muhimbi.com/2009/04/new-approach-to-solve-sharepoints.html
http://ddkonline.blogspot.com.au/2010/05/fix-sharepoint-very-slow-to-start-after.html

I just execute the vb script below as the article discussed to add the registry settings, without reboot the server, and it worked much faster.

const HKEY_USERS = &H80000003
strComputer = "."
Set objReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv")
strKeyPath = ""
objReg.EnumKey HKEY_USERS, strKeyPath, arrSubKeys
strKeyPath = "\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing"
For Each subkey In arrSubKeys    
objReg.SetDWORDValue HKEY_USERS, subkey & strKeyPath, "State", 146944
Next

How to use SharePoint workflow 2013 if this is not fixed.

I have been checking out the SharePoint workflow 2013, which gave many exciting new features and I am all up to try it in demo. Then I found this article here. It said if you develop a workflow in Visual studio 2012 and deploy it, then any later changes for the workflow will not get updated in the SharePoint. It seems that you can only develop the workflow once and if it is wrong, you can not update it, you need to start again for a new one. WTF.

https://connect.microsoft.com/VisualStudio/feedback/details/779905/sharepoint-2013-workflow-deployment-doenst-update-workflow-definition

Luckily, there is a fix as the workaround tab mentioned from the link above.
A vssphost5.exe process needs to be terminated before deploy.

And this link,
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/8420797e-cb85-4949-9e0e-5060a9060c10/how-to-update-copy-of-sharepoint-2013-azure-workflow

And the official known workflow issues article is a must read.
http://office.microsoft.com/en-us/help/sharepoint-server-2013-known-issues-HA102919021.aspx#_SharePoint_Designer

Crate custom task form in SharePoint 2013 workflow

With the SharePoint 2013 workflow, the InfoPath based form is not used for task forms, instead custom aspx page will need to be created. This is actually a good move to give developers back the flexibility to extend it more.

The blow is so far the best article to teach how to do it.

http://sp2013.pro/2013/03/creating-spd-2013-workflows-part-23-implementing-custom-asp-net-task-form/#more-124

SharePoint 2013 and IE 10 work together

I access the SharePoint 2013 sites using IE 10, then if I tried to go to Site Settings page, I got this error,

An error has occurred with the data fetch. Please refresh the page and retry.

F12 to open the developer tools I can see it is a SCRIPT5: Access is denied error.

There are a few options to look at,

1. Check IE10 browser compatibility
Hold ALT-T, and go to Compatibility view settings to set up the SharePoint site.

2. Disable Tracking Protection

3. Add the site to the trusted sites from internet options

Correctly add the javascript intellisense for SharePoint 2013 for Visual studio 2012

In visual studio 2012, it is quite easy to add a javascript intellisense.

Add a scripts folder and in the folder add an _reference.js file to reference the javascripts.
Such as,
/// <reference path="/LAYOUTS/My_custom_package/jquery-1.10.1.js" />
For adding the SharePoint 2013 client javascript library, the below codes are needed.
/// <reference name="MicrosoftAjax.js" />
/// <reference path="~/_layouts/15/init.js" />
/// <reference path="~/_layouts/15/SP.js" />
/// <reference path="~/_layouts/15/SP.Runtime.js" />
/// <reference path="~/_layouts/15/SP.UI.Dialog.js" />
/// <reference path="~/_layouts/15/SP.Core.js" /> 
 

Sharepoint 2013 Search Experience

It is generally good experience in SharePoint search. However there are a few issues needs to wait maybe until the service pack out.

1. The search result web part is not able to return custom managed property, it seems to be an existing bug that any extra managed property can not return the data even it is shown on REST.
http://social.msdn.microsoft.com/Forums/en-US/sharepointsearch/thread/f53c87d0-af81-445c-8338-1bfea6ca780e

2. Event the document id feature is activated, the docId managed property is only returning integer even after a full crawl. A second managed property has to be created to point to the previous crawl property as ows__l_docId, then it works.

3. For the content search web part, there are limitation to allow five managed properties in the design template, and the paging has no page numbers.

4. When the search crawling is stuck in "Full Crawling" status, reboot worked.

And some references regarding to search,
http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/3878d445-9772-4852-aea2-4f35d072b60e

SharePoint Load ClientContext

This how to load ClientContext

var clientContext;
var website;

SP.SOD.executeFunc('sp.js', 'SP.ClientContext', sharePointReady);

// Create an instance of the current context.
function sharePointReady() {
    clientContext = SP.ClientContext.get_current();
    website = clientContext.get_web();

    clientContext.load(website);

    clientContext.executeQueryAsync(onRequestSucceeded, onRequestFailed);
}

function onRequestSucceeded() {
    alert(website.get_url());
alert(g_wsaSiteTemplateId );
}
function onRequestFailed(sender, args) {
    alert('Error: ' + args.get_message());
}