DataView WebPart / XSLT Customer Parameter Bindings and using its data

To introduce a customer parameter, simply use the dialog:

image

 

after creating a new parameter, ensure that the xslt has the following entries:

1. At the bottom:

<ParameterBinding Name="TitleInner" Location="None" DefaultValue="Our Clients"/>

2. At start:

<xsl:param name="TitleInner">Our Clients</xsl:param>

 

Then you can consume/use the parameter as follows:

<div class="col-lg-12">
  <h2><xsl:value-of select="$TitleInner" /></h2>
   <hr />
</div>

Viewing SharePoint 2010 Version information (Product, Cumulative Update, Hotfixes Version)

To view current product version information on a SharePoint server environment use the attached PowerShell tool:

1. Extract this tool (zipped) to a folder

2. Right click on the “Get-sharepointversion.cmd” and choose “Run as administrator”

3. Wait until finished

E.g. Information:

E.g.1 – Environment-1 E.g.2 – Environment-2
Foundation Build : 14.0.6114.5000

Foundation KB    : KB2597014

SP Build         :

SP KB            :

Release Name     : December 2011 CU

– SP2010 Version is 14.0.6113.5000

Foundation Build :

Foundation KB    :

SP Build         : 14.0.6113.5000

SP KB            : KB2596998

Release Name     : December 2011 CU

Foundation Build : 14.0.6117.5002

Foundation KB    : KB2597136

SP Build         :

SP KB            :

Release Name     : February 2012 CU

– SP2010 Version is 14.0.6117.5000

Foundation Build :

Foundation KB    :

SP Build         : 14.0.6117.5000

SP KB            : KB2597150

Release Name     : February 2012 CU

See also – https://consultantpoint.wordpress.com/2014/11/24/quick-way-to-get-sharepoint-version/

Download here:

 Get-sharepointversion.zip

Creating a Feature for the Site Actions Menu in SharePoint 2010

Overview

You can add a custom menu item to the default Site Actions menu in Microsoft Windows SharePoint Services by creating a Feature with a CustomAction element. In this way, you can add custom commands to the default SharePoint user interface. These commands are available to users as they move between pages on a SharePoint site. When you create a Site Actions menu item, you can configure it to redirect the user to any URL. For example, you can redirect the user to another Web site. You can also redirect users to a custom application page that allows them either to see a custom display of data, or to perform custom operations on the content within the current site.

Code It

  1. Create a new Project in VS 2010 and under SharePoint (left) select Empty Project.
  2. Now enter the url of your SharePoint site for debugging and select deploy as a farm solution.
  3. Now, once you have the project open, right click on the Feature folder and Add a new feature.
  4. SharePoint automatically adds a feature and names it as Feature1. You can however change the feature name to something like CustomActionFetaure.
  5. With this you will have a feature designer opened in front of you set the Title description and scope of the feature.
  6. Now right click on the Project and add a new Item. In the Add New Item dialog, select Empty Element to create a blank element file.
  7. Add the below Code to the element.xml file.

    <?xml version="1.0" encoding="utf-8"?>
    <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
    <CustomAction
    Id="viewSiteManager"
    GroupId="SiteActions"
    Location="Microsoft.SharePoint.StandardMenu"
    Sequence="1000"
    Rights="ViewListItems,ManageAlerts" Title="Manage Content and Structure" Description="Reorganize content and structure in this site collection.">
    <UrlAction Url="~site/_layouts/sitemanager.aspx"/>
    </CustomAction>
    </Elements>

  8. Build the Project. Open the feature.xml file and verify that if contains the reference to the element.xml file.
  9. Now Deploy the wsp and activate the feature in your site.

Read It

When you create a CustomAction element, you must add an inner UrlAction element that contains a Url attribute. When you redirect the user to an application page, such as SiteManager.aspx, you must consider whether you want the application page to run inside the context of the current site or the current site collection. In the following example, the dynamic token ~site is added to the beginning of the URL. When Windows SharePoint Services parses this CustomAction element and creates the menu item, it replaces ~site with the actual URL of the current site.

"~site/_layouts/sitemanager.aspx"

The key to security trimming your custom action is the Rights attribute. This attribute allows you to specify SharePoint permissions that the user must have for the action to be visible. This can be a comma delimited list. For example:

Rights="ViewListItems,ManageAlerts"

When more than one value is specified, the set of rights are treated with an AND. This means the user must have all of the specified rights for it to be visible. Here is a list of the valid Microsoft.SharePoint.SPBasePermissions you could use:

http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions

Also, When you create the element for a custom menu item in the Site Actions menu, you have the option to configure it so that it is shown only to users who have administrative permissions. Note in the following example the addition of a new attribute named RequireSiteAdministrator.

RequireSiteAdministrator="TRUE"

When you add the RequireSiteAdministrator attribute, Windows SharePoint Services does not show the menu item to users who do not have administrative permissions. For a CustomAction element in a Feature that is scoped at the site-collection level, the menu item appears only for the site collection owner or administrator. For a CustomAction element in a Feature that is scoped at the site level, the menu item appears only to those who have administrative permissions within the current site.

Finally

siteaction

Related Link: http://blogs.msdn.com/b/edhild/archive/2008/01/16/how-to-add-security-trimming-info-to-custom-actions-in-sharepoint.aspx