SharePoint Interview Question Experience developer Part 1

  1. What is variations in sharepoint
  2. What is claim based authentication and how it works with the SharePoint in back ground
  3. What are features provided by document library
  4. What is mms? How can you make MMS terms Multi lingual?
  5. What is a claim based Authentication and how does it exactly authenticate?
  6. App fabric and why it is used?
  7. Difference between workflow architecture in SharePoint 2010 and SharePoint 2013?
  8. How can you publish 2 different versions of contentypes on specific sites?
  9. How can you make different versions of content types and what are the best practices for upgrading contentypes?
  10. Explain Distributed cache systems in SharePoint 2013?
  11. Explain MUI in SharePoint 2013?
  12. How to retrieve 15 thousand records from a list without setting throttling?
  13. Best practices for creating a site with pre created components.(example site definitions)?
  14. What is Feature Stapling and how it’s done at code level
  15. Explain App model
  16. Explain authentication and authorization in apps
  17. How to create context for high and low trust apps?
  18. How can you allow external users to use your o365 workflow
  19. Can you call a workflow in a workflow? if yes how?(Syntactically)
  20. What caching mechanism have you used with the SP
  21. What is STS and why to use it, why not use configuration list
  22. What is bcs and how you can move BCS from development server to production server
  23. Drop off library feature names?
  24. How will query the versions of the document
  25. How to store farm level  configuration in SharePoint
  26. What caching mechanism have you used with the SP
  27. What are the restapi endpoints in SharePoint
  28. What is odata and its filters?
  29. What is the endpoint to query the search using rest search?
  30. Which one to choose between rest vs csom
  31. Which one is faster webpart or visual webpart.
  32. Which class is responsible to create client context in high trusted apps.
  33. How will you ensure user with read permission can write into the list using Server object model and in Apps

Namespace prefix ‘xsd’ is not defined

While working with infopath form we have encountered the below issue while viewing the infopath form in IE 11.

Unexpected System.InvalidOperationException: Namespace prefix ‘xsd’ is not defined. at System.Xml.Serialization.XmlSerializationReader.ToXmlQualifiedName(String value, Boolean decodeName) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read1_
Object(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.
Read2_DictionaryEntry(Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.

Solution 1:

Here are the steps that we applied on IE to resolve the issue.

  1. Open Internet Explorer
  2. Click on Tools at the top and select Internet Options
  3. Click the Security Tab
  4. Click Local Intranet
  5. Click Sites
  6. Click Advanced and all of the intranet sites will reappear in the websites box, select our site and click on Add button. Make sure there is a check box in the Require server verification box
  7. Click Close
  8. Click Ok
  9. Click Ok and you’re done
  10. Then, try accessing the infopath form again.

Solution 2:

  1. Take Backup of pickerdialog.master present in 14 hive inside layout folder(“C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\pickerdialog.master”)
  2. Edit pickerdialog.master in notepad and add below tag inside Head tag

<meta http-equiv=”x-ua-compatible” content=”IE=8″ > just after the
<meta name=”GENERATOR” content=”MicrosoftSharePoint” />

  1. Save the file and perform IISRESET

Solution 3:

  1. Locate the file formserver.aspx present under 14 hive > Template > Layout
  2. Take backup of this file formserver.aspx
  3. Edit this file and add below line of code under <body> tag

      <SharePoint:FormDigest runat=”server” />

       For example,

       <body runat=”server” id=”PageBody”>

       <SharePoint:FormDigest runat=”server” />

  1. Save the file and perform IISRESET

Open List form as modal dialog box SharePoint 2013 OOB

In share point 2013 list when you click on new item page open as full page not as dialog box as in share point 2010.

To open list pages(forms) in modal dialog box go to advance setting of the list and set yes to launch form in dialog in Dialogs section.

download (1)

You can use server side object model to open list form page to launched in a modal dialog


and to open as full page set


This page allows a limit of 200 controls, and that limit has been exceeded.

This issue occurs when the number of controls present in page(including master page control) exceed default limit set for the web application.By default it set to 200.

In my case i had application page with many controls and when i tried to view page it throws an error “This page allows a limit of 200 controls, and that limit has been exceeded”


To resolve this issue steps are as follows

1. open the web.config file of the web application(located in inetpub)

2.Take the back of web.config file and open the file in notepad or any text editor

3. find the tag

<SafeMode MaxControls=”200″ CallStack=”false” DirectFileDependencies=”10″ TotalFileDependencies=”250″ AllowPageLevelTrace=”false”>

and Change the max controls attributes to higher than 200, I set to 1500,increase until it resolved the issue. 

Hope this help

Start Stop SharePoint timer Service using command line

Many time while working withe timer job to get the new  code changes we need to restart timer service.

Below are the cmd command that can be used to stop and start timer service

To stop Timer service:

net stop SPTimerv4

To start timer service

net start SPTimerv4

To stop SharePoint Administration service:

net stop SPAdminV4

To start SharePoint Administration service

net start SPAdminV4

Difference between SPList.ItemCount and SPList.Items.Count

Many times we encounter difficulties to choose between SPList.ItemCount and SPList.Items.Count while querying the share point list.

So after reading this blog,you will be in better position to choose between SPList.ItemCount and SPList.Items.Count 😉

SPList.ItemCount: If you want to get the count of list items including folder and sub folder,use SPList.ItemCount property of the list.

SPList.Items.Count: The SPLISt.Items property returns all the files in a document library/List, including files in sub folders, but not the folders themselves.SPList.Items returns the list items by running a query with Scope=Recursive ViewAttribute.Hence if you want to get only the count of items then use SPList.Items.Count

Permission:As SharePoint provide item level permission,to use SPList.Items.Count code must be running with the full permission else it will result into access denied. SPList.ItemCount not required as such permission.

Performance:Performance wise  SPList.ItemCount  is faster as it is static property of SPList. SPList.Items is slower as it has to  first get the data then do the counting.

However SPList.ItemCount occasionally return unexpected It is best practice is to use one of the GetItem* methods of SPList to return a filtered collection of items.