SharePoint For Developers

In SharePoint search the most of time people annoying that actual content and search content not in Sync. So the search administrator keeps hitting head on the wall and putting same excuse in front of stakeholders “please wait for the next incremental crawl, most of the time :)”. As we know we already have two content crawling methods first is “ Full Crawl ” and second is “ Incremental crawl ”. Disadvantage of the “ Full Crawl ” and “ Incremental Crawl” as both can’t run in a parallel i.e. the content change during the crawl, it required next incremental crawl. So what is new in continues crawl? The content source that using continues crawl that run in parallel . The default waiting time is 15 min. So the default wait time can change via PowerShell , no UI for that. Now the content is up to date most of the time. This crawler only for SharePoint content source, so the job of the SharePoint administrator need to identify those content which are keep updating on the regular

Yammer is Enterprise Social Network service that was launched in 2008 and sold on Microsoft in 2012. Yammer is an enterprise collaboration tool , used for private communication within organization. Access to yammer network determined by a user’s internal domain so that only individuals with appropriate email addresses may join their respective networks. Yammer Certification To truly master this product you need to spend some time on it, may be even spend some time on certification. There are different certificate found on yammer certification page . Yammer power user certification Yammer community manager certification Yammer trainer certification Yammer administrator certification  Exam yet to come   Yammer developer certification  Yammer training Resource/Yaminars   You can watch the some Yaminars and also read the yammer training resources .If you do not have any experience with using Yammer it might require a bit more time and reviewing some of the options,

Following are the limitation of SharePoint software. Limit Maximum Value Limit Type Web application 20 per farm Supported Zone 5 per web application Boundary Managed path 20 per web application Supported Solution cache size 300 MB per web application Threshold Application Pools 20 per farm Supported Number of content databases 500 per farm Supported Content database size (general usage scenarios) 200 GB per content database Supported Content database size (all usage scenarios) 4 TB per content database Supported Content database size (document archive scenario) No explicit content database limit Supported Content database items 60 million (includes documents and items) Supported Site collections per content database 10,000 Supported Site collections per farm 750,000 Supported Web site

In SharePoint, most of the customization can be achieved without developing/writing custom solution. Some time we required a customization and during this customization the main concern on quality solution; we ensure the best practice & rules must be defined and follow. These rules and policies must be defined (e.g. in customization policies) and must be accepted by all involved people, like developers, architects and also by the business side because these policies may limit the adaptability of SharePoint. So there is no such a automated process that validate those rules during development face. To deliver the quality standards as end result during earlier development face. Tool is created by Matthias Einig and Torsten Mandelkow   and name of the tool is SharePoint Code Analysis Framework(SPCAF) . SPCAF Essential tool to ensure SharePoint code quality. SPCAF will analyze assemblies and all the XML for your SharePoint packages (wsp’s), and all other controls and m

SharePoint 2013 new app model has been introduced by Microsoft. To develop the Apps there are some of the good client side scripts are available. We can create the responsive application with the help of these libraries. The libraries are well known and most of the big companies like Yahoo, Mozilla etc. are using these framework. As we already knows that Microsoft heavily emphasise on Client side scripting that’s why Microsoft did a investment to improve the client side framework for SharePoint 2013. As per SharePoint 2013 server side API, hardly not much change. No doubt if you say it is a feature of development. There are list of many client side JavaScript. Not taking much of your time, following are the list of Client side Presentation Framework. Presentation Framework 1.        Durandal 2.        Anguer 3.        Ember Rich Data Framework 1.        Breeze There are plenty of libraries are available. One of the nice blog “ Single page App ” written by Andrew Conn

As SharePoint 2010 perform the entity extraction & data cleansing we required the FAST document processing stage called pipeline extensibility stage, it is no longer available. It was replaced by content enrichment web services.  As Microsoft says about it.  Search in SharePoint 2013 enables users to modify the managed properties of crawled items before they are indexed by calling out to an external content enrichment web service. The ability to modify managed properties for items during content processing is helpful when performing tasks such as data cleansing, entity extraction, classification, and tagging.   Please go through with the below links for more details. http://msdn.microsoft.com/en-us/library/jj1639 82.aspx http://msdn.microsoft.com/en-us/library/jj163968.aspx There are some of the good article, that describe the advanced content enrichment web service Advanced Content Enrichment in SharePoint 2013 Search Calling WCF using Content Enrichment

Recently I read the post written by Steve Peschka which is on “Security in SharePoint App”. If you want to understand about the App security please go through with it. ·          Security in SharePoint Apps - Part 1 ·          Security in SharePoint Apps - Part 2 ·          Security in SharePoint Apps - Part 3 ·          Security in SharePoint Apps - Part 4 ·          Security in SharePoint Apps - Part 5 ·          Security in SharePoint Apps - Part 6 ·          Security in SharePoint Apps - Part 7 ·          Security in SharePoint Apps - Part 8

Workflow (Business Process Automation) Workflow is a process of automation of the manual process. Workflow makes the complex process more easy, reliable and redirect the labor and contains cost. Business Process tools Large enterprise resource planning system Middleware to integrate existing price General purpose tool to create the simple automation example: Excel. SharePoint Business Process Automation SharePoint: MS Office tightly coupled with SharePoint. So Track the date in the SharePoint list & notify the uses with changes track task, contact list and event with outlook. Workflow to attached task and store document to the document list. K2: SharePoint Workflow process can be extended using K2.  Nintex: SharePoint only workflow solution for complex workflow and integrate with InfoPath. SharePoint Business Automation Process List  Assign Task Track issue Track Process SharePoint Alerts  Notify users of changes in list and libraries User can

In SharePoint 2013 there are no visual best bets/best bets, keywords replaced with promoted result with Intent based search experience. When condition of query rule trigger based on the rule promoted , result block and result rank applied to the search. why changed to promoted result? When client comes and says, I wanted to display my result i.e. promote my results in SharePoint search center what search analysis replay to client, yes we will add visual best bets or best bets. The really client not understand the technical words best bets and also it not make any sense. Microsoft decided to change the visual best bets to “promoted results”. Query Rules can be created at the Search Service Application, Tenant, Site Collection or Site level. Query rules composed to three components. Condition: When to apply the rules? There are list of condition available, we can create the rule based on the keywords. We can also get the keywords from term store (MMS). For POC p

SharePoint 2010 getting search keyword: we were writing a custom code to get the Search keyword & best bets, we used the FAST Search Proxy. The big bug found & that mentioned below. Special thanks for Mikael Svenson. He already did a lot of research on it. var ssaProxy = (SearchServiceApplicationProxy)SearchServiceApplicationProxy.GetProxy(SPServiceContext.Current); if ( ssaProxy.FASTAdminProxy != null ) Error line { var fastProxy = ssaProxy.FASTAdminProxy; KeywordContext keywordContext = fastProxy.KeywordContext; var searchGroup = (from x in keywordContext.SearchSettingGroups wherex.Name==SPContext.Current.Site.ID.ToString() select x).First();  } Above code was not working, the problem was Fast Search Service Proxy unable to connect with the search service. The FASTAdminProxy reads it’s WCF configuration from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\FASTSearchAdmin\ContentCollectionService\client.config. Servic

Automatically created when site column created and used (the must be stored in the content database using this column). Crawl properties now crated at the site collection level. Earlier only available at the application level. Crawl properties & manage properties created with specific naming convention, as mentioned in the attached link MSDN . Automatically created crawl properties sortable and refinable are turned off and property with text data type. There are list of OOB Manage Properties available at site collection level with different-2 data type start with name Refinable<datatype>00 .. Refinable<datatype>100 to you can use this to make achieve Sorting and refinable by map crawl property one of manage property give it alias.  There is confusion with crawl property, actually in SharePoint 2013 two crawl property created when ever a new site column created and it used. I have created the site column name "MyCustomDate". SharePoint 2013 two

Problem In SharePoint 2010, we do not have OOB web part that get back aggregate results i.e. results more than one site collection. The Content Query Web part displays aggregate list content (data from multiple lists) from within a single site collection. Why not Custom Web part? If the number of site collection is increase, the custom code will cause the issue and this end up with performance or may have a chance for a memory leak. Why Content Search Web part? SharePoint 2013 Content Search web part introduced by the Microsoft to break the site collection boundary problem.Web part displays cross site collection aggregation results. It is OOB solution and fully based on Search(Indexed content) the more often crawl run, the more up to date content. Content Query Web Part (CQWP) Content Search Web Part(CSWP) The Content Query Web Part allows you to display content from single site collection. The Content Search Web Part breaks the site coll

Result Types: Each Search result item render differently. In search result page, whatever renders on the page, it is display on the basis of search result and each control has its own result template like Refiners , Core Result, Search Vertical, Search Box  and Hover card . Each item in a search result page use different " Display Template ". Every web part has a option to set result type template. By default SharePoint 2013 comes up with some default list of template.Apart from the search web part there is another web part called Content search web part(CSWP) has its own result template to render the results. Following are the list of default template that are being used by web part. There are may mores display template but I mentioned the common one.  Search Navigation : Search Results Default Search Box: Default Search Box Core Result (Everyone Search vertical): Default Result Refiner control default : Vertical Content Search WP : Control template:  

Result Source : SharePoint 2013 comes with Result Source, "which is a replacement of SharePoint Scopes and federation locations" . Apply query to transform a corpus subset. In SharePoint 2010, the scopes only are created at the application level to overcome this problem. Result source can be created at Application Level, Site Collection Level and Site Level . Now the every site owner can creates the result source at Application, site collection and site. Site Level Site Collection Level Application Level So site collection result source available to all the sub site, and site can have its own result source. Once it created user create the new Search Vertical and update the core result web part. Following are the steps to create the Result Source. Go to the settings -> Site Settings -> Under Search -> Click to the Result Source -> Click to Add Result Source You need to give the name of the Result Source In Protocol section -> Se