Know More

Hi SharePoint friends , I hope you all enjoyed my last post on “ Authentication & Authorization ”. In this post I will discuss about the features that have been removed in SharePoint 2013 which was available on SharePoint 2010. Visual Upgrade: You could use this feature to upgrade from MOSS 2007 to SharePoint 2010 to give Site Collection Owner and Site Owner to preserve the existing user interface temporarily while still upgrading the infrastructure, content databases, site collections and features to the latest version. Now this feature is replaced with “ Deferred Site Collection” upgrade which is considered as more comprehensive upgrade process than visual upgrade. Visual Upgrade preserved only the master pages, CSS files and the HTML files but the Deferred Site Collection upgrade with preserve much more including SPFeature functionality. With the deferred site collection upgrade you can use the UI feature from the previous version more seamlessly than with the visual

Hi SharePoint friends , Today I am going to give u a short and sweet about the authentication and authorization in SharePoint 2013 and the improvements in SharePoint 2013. The contents available in this post are taken various sites and MSDN. What is authentication in SharePoint? It is a provider that validates the users identity who request access to the web application, Once validated it issues the authenticated user a security token that encapsulates a set of claims based assertions about the user and is used to verify a set of permission assigned to the user. What is authorization in SharePoint? It is the process that determines the defined operation on a specified resource within the web application of the authenticated user. I think you are very clear about the authentication and authorization concept in SharePoint. The following are the recommended methods of authentication in SharePoint 2013 Windows claim Security Assertion Markup Language (SAML)-based claims Form-

Hi SharePoint Friends,   I would like to discuss some cool stuffs for developing custom “Tool Parts” for SharePoint 2010 Visual web part. “Tool Part” is nothing but the set of controls that are required for your web part which works based on the tool part properties. It will be available as a new section in the web part properties area. There are two ways for developing a Visual Web part with custom tool part 1. Designing the entire tool part using the server side code. 2. Designing the tool part using user controls In this part, I will drive you thru O ption 1 . R u ready, lets get started. Step 1: Create a “Empty Project” using Visual Studio 2010 and name it as “CustomToolpartOtion1” and choose the deployment type as a “Farm Solution” . You should see a similar project structure in VS 2010. Step 2: Open “VisualWebpartwithTP1.cs” file and write the below mentioned code. The above mentioned code is to declare a property which has to be rendered in the web part proper