Home > SharePoint Products and Technology > SharePoint QuickLaunch Control

SharePoint QuickLaunch Control


Write up on SharePoint QuickLaunch Control

Customizing QuickLaunch Control through the SharePoint wizard:
1] Site Actions > Site Settings > Modify Navigation
2] Subsites and Pages check boxes to display items underneath them.
3] Enabling Sorting On.
4] Global Navigation for Displaying the Horizontal Navigation menu.
5] Current Navigation.
   I] Display the same navigation items as the parent site.
   II] Display the current site, the navigation items below the current site, and the current site’s siblings.
   III] Display only the navigation items below the current site.
6] Navigation Editing and Sorting for Adding/Editing/Deleting Headings, Links.

Now the above stated configuration is easy, simple and not mint for complex dynamic links.
For such case we definately need to write a awesome code.

Controlling the Levels of Nodes creation under Parent Node:
For this task we need to edit the QuickLaunch Control settings in the SharePoint Designer as follows:
1] Find html tag named “SharePoint:AspMenu” inside the default.master page of Sharepoint site
   This page can be found http://servername:portnumber/_catalogs/masterpage/default.aster path
2] The “SharePoint:AspMenu” has following attributes
    id=”QuickLaunchMenu”
    DataSourceId=”QuickLaunchSiteMap”
    runat=”server”
    Orientation=”Vertical” : Controls orientation of QuickLaunch
    StaticDisplayLevels=”2″: Levels of Nodes creation under Parent Node
    ItemWrap=”true”        : Wrap text either true or false
    MaximumDynamicDisplayLevels=”0″
    StaticSubMenuIndent=”0″
    SkipLinkText=””
3] StaticDisplayLevels determines the levels of nodes creation, change its value and save the page and publish page.

Programmatically Adding/Editing/Updating/Deleting the Navigation nodes of QuickLaunch control.

Approaches for Developing the code that takes care of Adding/Editing/Updating/Deleting the Navigation nodes of QuickLaunch control.
1] Web part.
2] Extending the default.master by default.master.cs which is actually a .dll project.
3] ASP.NET User control (.ascx) file.
of the above approaches I prefer to go with user control bcz,
1] Its easy to develop and deploy at following location
 “c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\CONTROLTEMPLATES
and add the reference in the master page.
2] Easy to uninstall from the site.
3] Easy to install for different site on the server.
4] Light weight as compared to DLL projects.
5] Only drawback: can not debug the code as like to web part or default.master dll.

Next Post in context to QuickLaunch:Part II

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: