Know More

Hi Friends, today I am gonna show you one of the SPFx components developed by me. I hope, all the SharePoint users and developers are aware of the comment box in the modern page. The comments are tied to the page and are stored as metadata to the page. There are some features like a reply to the comment, likes etc., But there are some features missing in the comment box which may be required for the customers. One of my clients had asked for the feature of uploading files to the comment box. Based on the above use case and with many features, I took an initiative to develop an advanced comment box that can be used by switching off the out-of-box comment box. The custom comment box can be added to a page and once it is saved as a template, based on the template the page created will inherit the comment box. All the comments are stored in a separate list with the ' Page Title ' and ' Page URL ' as a key to the page comments. The component was developed using SPFx v...

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,   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 pr...

Hi guys, i hope u all enjoyed my previous posts. Here i would like to share some information regarding SPGridView in SharePoint. It is one of the most effective and advanced control in SharePoint. Many of them have used this control and they succeed in their part. As per one of the client requirement i have developed a application page with SPGridview and i have added Paging and Grouping. First i add only the paging with custom paging template it works fine. But, when i try to add the Grouping it throws an Unknown Error. I have searched all over the net and i have found the solution. If anyone has encountered this problem please change the EnableViewState property to false and it will work. Cheers...

Open SharePoint Designer. On the File menu, click New, point to SharePoint Content, and then click the Page tab. Double-click Master Page to create a new master page. Click Design to show the master page in design view. You should see header and left margin areas and several content placeholders in the master page. Click Code to show the master page in code view. Copy the Code into the Master Page. On the File menu, click Save As, provide a unique file name with the .master extension, and then save the file to the master page gallery (/_catalogs/masterpage) in your site collection. Cheers...

Introduction One of the first tasks that you must complete when configuring a Microsoft Office SharePoint Server 2007 Web site is to create one or more master pages. A master page contains references to elements that you can share across multiple pages in an Office SharePoint Server 2007 site, such as navigation, search controls, logon controls, and banner images. A master page can also contain the cascading style sheet (CSS) and ECMAScript (JScript, JavaScript) references that define the overall look and feel of your site. Commonly, every site—and therefore every page—in your site collection uses the same master page to present a consistent user experience across the entire site collection. Depending on your needs, you can use a different master page for one or for all of the sites in your site hierarchy to distinguish the various areas of your portal. Master Page Galleries When you provision a site collection in Office SharePoint Server 2007, the system creates a master page gallery ...

You can extend the navigation provider in Microsoft Office SharePoint Server 2007 by deriving a custom provider class from any of the default site map providers. Deriving from an Office SharePoint Server 2007 site map provider supplies several benefits such as navigation node caching and security trimming. The following code example derives from the PortalSiteMapProvider class and demonstrates how to add items to the site map provider. Although the site map provider classes have approximately twenty abstract or virtual methods, only a small number must be overridden and implemented in a custom site map provider. Create a Microsoft Visual C# class library project with following code, add the required references, and then build the project. using System;using System.Collections.Generic;using System.Text;using Microsoft.SharePoint.Publishing;using Microsoft.SharePoint.Publishing.Navigation;using System.Web;using System.Web.UI.WebControls;using System.Configuration; namespace MyCustomNav ...

To customize navigation, you should rely on the ASP.NET Site Navigation mechanism, because it provides a standard, consistent, and easily managed solution. Customizing Web Display Controls (Menu, TreeView, and SiteMapPath) : You can customize the look and feel of standard display controls by using cascading style sheets (CSSs). You can also write your own ASP.NET 2.0 controls and use them in Office SharePoint Server 2007 navigation. To learn more, see the Menu class documentation. Note : Office SharePoint Server 2007 also provides default navigation components that you can customize, such as the Content By Query Web Part and the Table of Contents Web Part. You can configure these two controls to present a custom selection of links. To implement your own site map provider, you can derive a custom provider class from any of the default site map providers. Office SharePoint Server 2007 includes several default providers. You can also derive a custom provider class from the SiteMapProvid...

The PortalSiteMapProvider object is the true source of hierarchical navigation data and it provides the data to the PortalSiteMapDataSource object. The PortalSiteMapProvider retrieves nodes from the Windows SharePoint Services 3.0 SPNavigation store. You use the SPNavigation object to create static links and groupings. After you provide static links and groupings, the application merges in dynamic items that represent Web sites and pages with the static links and groupings. Office SharePoint Server 2007 also applies security trimming so that users see only the navigation items to which they have permission to navigate. Declare named providers in the application's web.config file to make them widely accessible. Declarations of the two most important PortalSiteMapProvider objects— CombinedNavSiteMapProvider and CurrentSiteNavSiteMapProvider—are shown in the following code. add name="CombinedNavSiteMapProvider" description= "MOSS 2007 provider for Combined naviga...

The PortalSiteMapDataSource is a data source specific to Office SharePoint Server 2007 that retrieves data from the PortalSiteMapProvider object and exposes data according to the ASP.NET 2.0 hierarchical data source interface. The PortalSiteMapDataSource object specifies the name of the PortalSiteMapProvider object it uses to retrieve data through the ASP.NET 2.0 SiteMapProvider property. When the master page markup includes the DataSourceID="GlobalNavDataSource" attribute, the application returns a PortalSiteMapDataSource object. PublishingNavigation:PortalSiteMapDataSource ID="GlobalNavDataSource" Runat="server" SiteMapProvider="CombinedNavSiteMapProvider" ShowStartingNode="false" StartFromCurrentNode="true" StartingNodeOffset="0" TrimNonCurrentTypes="Heading" TreatStartingNodeAsCurrent="true" /> The properties are, ShowStartingNode - Affects whether the starting node is returned by ...

When you first create a site structure that includes a root or top-level site, more than one Web site, and pages and additional sites that are children of the top-level site, Office SharePoint Server 2007 creates two menus: a horizontal (top) menu, and a vertical (left) menu. Horizontal and vertical menus are declared in master page markup. The following example declares a horizontal menu. SharePoint:AspMenu ID="GlobalNav" Runat="server" DataSourceID="GlobalNavDataSource" Orientation="Horizontal" StaticDisplayLevels="1" MaximumDynamicDisplayLevels="1" /> The vertical menu is declared similarly, but uses different properties from the horizontal menu. These properties are identical to those available on the ASP.NET 2.0 Menu control. The following are the properties included by default in master page markup for both horizontal and vertical menus: DataSourceID - Specifies the data source control that provides the hierarchical...

Any declaration of Horizontal or Vertical menu instructions for navigation in XML for the master page, two classes are used to make the navigation work: PortalSiteMapDataSource PortalSiteMapProvider The PortalSiteMapProvider object provides the site hierarchy (navigation structure) and monitors the relationship between nodes.Many named instances of this site map provider are listed in the web.config file, and are also available through static properties on this class that the master pages in Office SharePoint Server 2007 deliver. Office SharePoint Server 2007 uses these named instances to provide data to the horizontal and vertical navigation menus. The application shares named instances across all Web requests on the current application domain. The class stores no session information. If necessary, session information is stored on the HttpContext class. The PortalSiteMapDataSource object maps navigation features from the PortalSiteMapProvider and filters navigation elements to de...

Most Web sites employ some form of customized user interface (UI) that provides users with visual clues on how to navigate in the site more easily, and find the information they need. Although the look and feel (or branding) can vary from site to site, the same basic navigation elements are usually present, such as navigation bars and menus that expose options a user can choose to navigate to a subsite or page. you can customize it through programmatically and also through the UI, including: Using the provider and data source APIs to customize the structure and behavior of vertical and horizontal menus. Understanding Navigation Settings UI options and using them to set up a site navigation hierarchy. Replacing the default navigation provider included in Office SharePoint Server 2007 with your own custom provider. Configuring multiple navigation providers for a site. Navigation Fundamentals To make it easy to build effective navigation elements such as horizontal and vertical menus and ...