SharePoint Developer

With SharePoint 2013 Microsoft has Introduced User License Enforcement Capabilities – that means different licenses can be assigned to different users based on Active Directory security groups that are added in.A group of admins for example would need features that are offered by Enterprise license but a group end users on the other hand can work with Standard license and would not need to pay more.By default the User License Enforcement is disabled and must first be enabled to begin assigning, using, and implementing user licensing capabilities.

With device channels in SharePoint 2013, you can render a single publishing site in multiple ways by using different designs that target different devices for example mobile devices etc.These device channels can each be given a different master page and CSS file to give users a more optimal viewing experience.

A new Column type “Related Items” has been Introduced in SharePoint 2013 where you can add reference to another Item or a document from any ListLibrary as a related entity to one of the Item using Related Items column.

SharePoint 2013 Introduces a Cloud App Model that enables you to Create apps. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint.

Most of the Solutions Should work fine but it is Recommended to Re-Create a Solution in Visual Studio 2012, Re-add all the features,Components and then deploy it to SharePoint 2013.

You can no longer add partial trust Solution Packages to the bin directory. Any files deployed to the bin directory must be full trust. Any deployment scripts needs to be updated to make sure that they specify the correct trust level. After the release of .NET Framework 4.0, the GAC was split into two, one for each CLR.

c:windowsassembly is the location for .NET versions 1.0 through 3.5 and c:windowsmicrosoft.netassembly is location for all the dlls for project Created in .NET Framework 4.0.

Creation of websites for information sharing and document collaboration will be enabled by Windows SharePoint Services. It provides additional functionality for MS Office system and other desktop applications. It also supports like a platform for the development of applications.

SharePoint is about Contents, so Content Type is a reusable collection of settings and metadata to represents a certain type of content. For Instance, a Student Content Type may have set of metadata like Student Enrollment ID, Name, year of enrollment etc.

Content Type in SharePoint facilitates to organize contents in more meaningful way. It supports inheritance of properties, behaviors and appearances.

When user writing custom code then it is not trusted, its failure causses on entire site. So the sandbox solution concept is used. In that case program is only written for particular site & solution is uploaded in the same site. The solution size limit is decided at the time of site creation & if size increases or code showing bad performance then it is easy to administrator to stop the working of solution.

SuiteLinksDelegate Delegate Control is responsible for displaying Links “NewsFeed, SkyDrive and Sites” in top right of the new SharePoint 2013 site (in the blue bar). These Links can be replaced by Overriding SuiteLinksDelegate Delegate Control using a Custom Control Created using Visual Studio.

SharePoint 2013 is the next Version of Microsoft’s famous Collaboration and Document Management Software called SharePoint.This Version follows SharePoint 2010 that was released back in May 2010.SharePoint 2013 was released (as Preview and RTM versions) with some new & exciting features such as Real Time Social Feed,Shredded Storage,SharePoint Apps,Cross-site publishing,Out-of-Box PDF support,Minimal Download Strategy and lot more.

The Analytics Processing Component runs two main types of analyses: Search analytics and Usage analytics. Search analytics analyzes content in the search index, and usage analytics analyzes the user actions.

SharePoint 2013 provides Support for both 14 Hive and 15 Hive. Both the directories are Created by default. So if you deploy a SharePoint 2010 Solution that refers to say _layouts folder, the reference will be made to 14 Hive and not 15 Hive by default. To make the solution refer to 15 Hive’s _layouts folder you need to Re-Create the Solution in Visual Studio 2012 and fix the _layouts reference to add ’15’ into it.

e.g.

14 Hive – _/layouts/custompage.aspx

15 Hive – _/layouts/15/custompage.aspx

Notice the reference of 15 in _layouts folder reference.

New “SPField.JSLink” property has been added to help specify any external JavaScript file Containing any Rendering logic for Out-of-Box or Custom field type. With JSLink developers can now Control the Rendering (the presentation and validation) of any Field (Custom or Out-of-box) on List forms as well as in Views by simply adding a reference to an External or deployed JavaScript file.

MasterUrl is used to change the layout of all use end pages but CustomMasterUrl is for changing the layout of admin side pages.

SharePoint Portal Services (SPS) has MUCH better document management. It has check-in, check-out, versioning, approval, publishing, subscriptions, categories, etc. STS does not have these features, or they are very scaled back. SharePoint Portal Services (SPS) has a better search engine, and can crawl multiple content sources. STS cannot. STS is easier to manage and much better for a team environment where there is not much Document Management going on. SPS is better for an organization, or where Document Management is crucial.