Custom PowerShell Commands

Posted by milap shah on Monday, November 23, 2009

To Create Custom Cmdlet, Your class can inherit from either PSCmdlet or Cmdlet class.

You could override below methods.
BeginProcessing-- Provides optional one-time, preprocessing functionality for the cmdlet.
ProcessRecord -- Provides record-by-record processing functionality for the cmdlet. It may be called any number of times or not at all, depending on the input of the cmdlet.

EndProcessing Provides optional one-time, post-processing functionality for the cmdlet.
StopProcessing Stops processing when the user stops the cmdlet asynchronously, such as by entering the key combination Ctrl+C.

To register this cmdlet you need to create a custom SnapIn by inheriting from PSSnapIn or CustomPSSnapin
You have to override below property.
Description: Supply short description of your Snap-in here.

Name: Supply name of your Snap-in here.
Vendor: Supply vendor information for your Snap-in here.
Cmdlets: This is where you provide collection of Cmdlets that need to be registered. I will discuss this in details.

Make sure you override the CmdLets property which should return all the Cmdlets that you want to register with PowerShell.
Example:
public override Collection Cmdlets

{
get
{
if (null == _cmdlets)
{
_cmdlets = new Collection();
_cmdlets.Add(new CmdletConfigurationEntry
("Get-Book", typeof(GetBookCommand), "AmazonPS.dll-Help.xml"));
}
return _cmdlets;
}
}

You need to mark the class with RunInstaller attribute

Then you have to install this snapin using installUtil 64 bit utility.
Then the snapin will be registered with the powershell.

Every time you open the powershell console. You have to run Add-PSSnapIn command.

Custom stsadm commnad in SharePoint 2007

Posted by milap shah

The STSADM.EXE utility enables many administrative operations in Windows SharePoint Services that cannot be done with the Central Administration application. See the article Stsadm.exe command-line tool (Office SharePoint Server) in Microsoft TechNet for details. With Windows SharePoint Services 3.0 you can extend the functionality of the STSADM utility by adding your own operations and command line parameters with simple projects using any .NET language.

Creating such a project requires two major tasks.

Create a class that implements the ISPStsadmCommand interface.
Inform STSADM about your extension by registering the class and its assembly.

Create a class that implements ISPStsadmCommand

Start a Class Library project in Visual Studio.
Add using statements for Microsoft.SharePoint and Microsoft.SharePoint.StsAdmin.
Use a namespace that follows the pattern CompanyName.TechnologyName.Feature.SubFeature. For example, AjaxInc.SharePoint.StsAdmin.CustomCommands. (See Names of Namespaces.)
Use a class name that expresses the common denominator of the new STSADM operations that you will be creating; for example, "SortCommands".
The class should inherit ISPStsadmCommand; with a declaration similar to the following.

public class SortCommands : ISPStsAdminCommand
Write the implementation of the GetHelpMessage method. See the example below.
Write the implementation of the Run method. See the example below.
Compile the project, using the namespace name as the name of the assembly.
Deploy the assembly to the global assembly cache; for example C:\Windows\Assembly.

Register the new class and assembly

Create a text file (UTF-8) named stsadmcommands.uniqueID.xml, where uniqueID is the name of your company or some other ID that ensures uniqueness on any server on which your extension of STSADM might be deployed. The XML declaration should read simply <?xml version="1.0" encoding="utf-8" ?>. The top-level element is <commands></commands>.
For each custom STSADM operation you created—that is, each possible value of the command parameter of GetHelpMessage and Run—add a <command/> element (inside the <commands> element) to your stsadmcommands file with the following syntax. (See the following example.) Change the version and culture values as needed.
```
<commands>
    <command 
        name="command_name" 
        class="fully_qualified_class_name, assembly_name, 
        Version=1.0.0.0, 
        Culture=neutral, 
        PublicKeyToken=value"/>
    
</commands>
```
Replace command_name, fully_qualified_class_name, and assembly_name with the appropriate values. (Do not include the ".dll" extension on the assembly name.)
Replace value with the public key token for your assembly which you obtain with these steps.
1. Right-click your assembly in the global assembly cache and select Properties.
2. On the General tab, copy the Public Key Token value.
3. Paste it as the value for PublicKeyToken.
Copy the stsadmcommands.uniqueID.xml file to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG.

Example

The following example shows the *.cs file and, below that, the stsadmcommands.uniqueID.xml file for a custom STSADM operation, called enumfeatures, that will list the features at a site.

using System;
using System.Collections.Specialized;
using System.Text;
using Microsoft.SharePoint;
using Microsoft.SharePoint.StsAdmin;

namespace MS.Samples.SharePoint
{
    public class SimpleCommandHandler : ISPStsadmCommand
    {
        public string GetHelpMessage(string command)
        {
            return "-url <full url to a site in SharePoint>";
        }

        public int Run(string command, StringDictionary keyValues, out string output)
        {
            command = command.ToLowerInvariant();

            switch (command)
            {
                case "enumfeatures":
                    return this.EnumerateFeatures(keyValues, out output);

                default:
                    throw new InvalidOperationException();
            }
        }

        private int EnumerateFeatures(StringDictionary keyValues, out string output)
        {
            if (!keyValues.ContainsKey("url"))
            {
                throw new InvalidOperationException("The url parameter was not specified.");
            }

            String url = keyValues["url"];

            SPFeatureCollection features = null;
            SPWeb web = null;

            try
            {
                SPSite site = new SPSite(url);

                web = site.OpenWeb();

                features = web.Features;
            }
            catch (Exception e)
            {
                throw new InvalidOperationException("Error retrieving url '" + url + "'.  Please check the format of your url, and ensure that the site exists.  Details: " + e.Message);
            }

            StringBuilder sb = new StringBuilder();

            sb.AppendLine("Features at '" + web.Url + "':\n");

            foreach (SPFeature feature in features)
            {
                sb.AppendLine(feature.Definition.DisplayName + " (" + feature.DefinitionId + ")");
            }
            
            output = sb.ToString();

            return 0;
        }
    }
}

Workaround for Double Hop issue

Posted by milap shah on Friday, November 13, 2009

public class UnImpersonator : IDisposable
    {
        [DllImport("advapi32.dll")]
        private static extern int RevertToSelf();

        private WindowsIdentity connectedUser = null;

        public UnImpersonator()
        {
            connectedUser = WindowsIdentity.GetCurrent();
            RevertToSelf();
        }

        void IDisposable.Dispose()
        {
            connectedUser.Impersonate();
        }
    }

//Sample Usage

protected void Page_Load(object sender, EventArgs e)
        {

            if (!IsPostBack)
            {
                using (new UnImpersonator())
                {
                    SqlConnection cn = new SqlConnection("Data Source=servername;Initial Catalog=Employee;Integrated Security=true;");
                    SqlCommand cm = new SqlCommand("select empid,empname from employee", cn);
                    cn.Open();
                    ddlEmployee.DataSource = cm.ExecuteReader();
                    ddlEmployee.DataTextField = "empname";
                    ddlEmployee.DataValueField = "empid";
                    ddlEmployee.DataBind();
                    cn.Close();
                    cn.Dispose();
                }
            }

        }

ListFieldIterator Control to render the sharepoint fields the way you want.

Posted by milap shah on Monday, November 9, 2009

This control renders each field in a list item with an appropriate control. A single line text field will be rendered as a text box while a lookup field will be rendered as combo box. This control resides in the Microsoft.SharePoint.WebControls namespace of the Microsoft.SharePoint.dll.

In its simplest way you can declare the control as follows:

<spuc:ListFieldIterator ID="TestListFieldIterator" runat="server"
                        ControlMode="Edit" ListId="{e2886b6e-4d63-4063-a02c-eac7fb3aef79}" />

This renders the first list item as follows:

listfielditerator-edit-mode

You can also set the ControlMode attribut to Display which renders the list item as follows:

listfielditerator-display-mode

If the control mode is set to New, empty controls are shown.

The way a choice field is rendered depends on the definition of the column. If you opted for a dropdown list when you created the column, the field is rendered as a dropdown. If you opted for check boxes for multi selection, the field is rendered as a list of check boxes:

choice-field

You can set different properties of the ListFieldIterator control:

ListId: This property must contain the id – which is a Guid - of the list you want to display.
ControlMode: Defines whether the controls are displayed in display mode, edit mode or new mode.
ExcludeFields: Specify the fields that don’t need to be rendered. Separate each field with ;#
Item: In code behind, you can retrieve the current list item by using this property.
ItemId: in code behind, you can retrieve the id of the current list item. But you can also decide which item to render by setting this attribute declaratively.

<spuc:ListFieldIterator ID="TestListFieldIterator" runat="server"
            ControlMode="Edit" ListId="{e2886b6e-4d63-4063-a02c-eac7fb3aef79}" ItemId="2" />

List: In code behind, you can retrieve the current list by using this property.
Template: you can set this property if you have deployed your own custom template to the 12\TEMPLATE\CONTROLTEMPLATES folder.

If you first add one or more controls to render fields from the list, and then add a ListFieldIterator control, it will automatically detect the fields already rendered and will not render them anymore. This can be useful if you want to change the order in which the controls must appear, or even more if you want to change the standard rendering of one or more fields (f.e. if you want to render one of the fields using Silverlight ).

<spuc:RichTextField ID="ContactTextField" runat="server"  
      ControlMode="Edit" ListId="{e2886b6e-4d63-4063-a02c-eac7fb3aef79}" FieldName="Description"/>

<spuc:ListFieldIterator ID="TestListFieldIterator" runat="server"
      ControlMode="Edit" ListId="{e2886b6e-4d63-4063-a02c-eac7fb3aef79}" />

listfielditerator-and-fields-before

This does not count for controls added AFTER the ListFieldIterator control.

Don’t forget to add a page directive in order to be able to use the control:

<%@ Register TagPrefix="spuc" Namespace="Microsoft.SharePoint.WebControls"
             Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

You can use this control in web parts and application pages but in general it is used in custom list definitions. When creating a custom list definition, the columns of the list will be rendered in a standard DisplayForm, NewForm and EditForm. If this standard rendering behavior does not satisfy your needs you can develop your own custom control templates. They need to be deployed in the 12\TEMPLATE\CONTROLTEMPLATES directory and need to be referenced in Forms element of the schema.xml of the custom list definition:

<Forms>
    <Form Type="DisplayForm" Url="DispForm.aspx" SetupPath="pages\form.aspx"  WebPartZoneID="Main"/>
    <Form Type="EditForm" Url="EditForm.aspx" SetupPath="pages\form.aspx" Template="CustomersForm" WebPartZoneID="Main"/>
    <Form Type="NewForm" Url="NewForm.aspx" SetupPath="pages\form.aspx" Template="CustomersForm" WebPartZoneID="Main"/>
</Forms>

The Template attribute must contain the name of the template that is defined in an ascx control deployed in the 12\TEMPLATE\CONTROLTEMPLATES folder.

Some Important Links

Posted by milap shah on Friday, November 6, 2009

http://techtrainingnotes.blogspot.com/2008/02/sharepoint-hiding-menus-not-using.html

Add Custom Actions to UI

Default Custom Action Locations and IDs

Content Types

Hide Multiple Upload menu from a Document Library

Posted by milap shah on Tuesday, November 3, 2009

Use this javascript

<script language="JavaScript">
_spBodyOnLoadFunctionNames.push("HideNewIcons");
function HideNewIcons()
{
var doc = document.getElementsByTagName('ie:menuitem');
for(var i=0;i<doc.length;i++)
{
if(doc(i).id.match('MultipleUpload'))
{
doc(i).style.visibility="hidden";
}
}
}
</script>

Add Custom Menus using CustomAction

Posted by milap shah

Following are few examples of how to add a new menu to EditControlBlock,SiteSettings Gallary,SiteActions menu.

<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<CustomAction
    Id="NewEditItemMenu"
    RegistrationType="List"
    RegistrationId="101"
    Location="EditControlBlock"
    Sequence="106"
    Title="MY ECB ITEM">
    <UrlAction Url="/_layouts/viewlsts.aspx"/>
</CustomAction>

<CustomAction
   Id="NewSiteSettingsGallary"
   GroupId="Galleries"
   Location="Microsoft.SharePoint.SiteSettings"
   Sequence="106"
   Title="MY ECB ITEM">
    <UrlAction Url="/_layouts/viewlsts.aspx"/>
</CustomAction>

<CustomAction
   Id="NewSiteActionsMenu"
   GroupId="SiteActions"
   Location="Microsoft.SharePoint.StandardMenu"
   Sequence="106"
   Title="MY ECB ITEM">
    <UrlAction Url="/_layouts/viewlsts.aspx"/>
</CustomAction>

</Elements>

Using ControlAssembly to Add New Menus to any GroupId

Check my other blogpost

Hiding Menus in SharePoint

Posted by milap shah

Alternatives

If you want to hide a menu on perticular page then use CEWP(Content Editor WebPart) and put javascript in Source Editor to hide the menu. The id of the menu can be found using ViewSource from the browser. For example to hide siteactions menu from a perticular page use below javascript. Note that to execute any javascript after onload you haveto use _spBodyOnLoadFunctionNames function.

<script language="JavaScript">
_spBodyOnLoadFunctionNames.push("HideNewIcons");
function HideNewIcons()
{
var doc = document.getElementById('siteactiontd');
doc.style.visibility="hidden";
}
</script>
Modify default.master page and put it inside that file.
Use a Feature.
If you want to control the hiding of the menus by using a Feature so you can turn them on and off at will, and at the farm, application, site collection or site level the you have a little more work to do, but not too much.
I will return here later and add a full step by step, but here's the code you will need:

A SharePoint Delegate control:

Add this to the bottom of your Master Page just before the </body> tag (The ControlId is up to you, but needs to match the Id used in the elements file):
<SharePoint:DelegateControl runat="server" ControlId="MiscControls" AllowMultipleControls="true"/>

A .Net User Control: HideMenus.ascx
<%@ Control Language="C#" ClassName="HideMenus" %>

<script language="JavaScript">
var doc = document.getElementsByTagName('ie:menuitem');
for (var i = 0; i < doc.length; i++){
itm = doc(i)
if (itm.id.match('MultipleUpload')!=null itm.id.match('OpenInExplorer')!=null)
{
itm.hidden=true;
}
}
</script>

A feature file: Feature.xml
<Feature
Id="531F15CD-A646-45e5-AB61-4F8DF89C29D9"
Title="Hide Menus"
Description="Sample feature to hide selected menus (MAX Technical Training demo)"
Scope="Web"
Hidden="FALSE"
xmlns="http://schemas.microsoft.com/sharepoint/"> <ElementManifests>
<ElementManifest Location="elements.xml" />
</ElementManifests>
</Feature>

An elements file: Elements.xml

<Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <Control ControlSrc="~/_controltemplates/HideMenus.ascx" Sequence="100"
Id="MiscControls">
</Control>
</Elements>

SharePoint CustomAction Identifiers

Posted by milap shah

Id ReportListActionsMen Extend Unextend Delete ManagedPaths EmailSettings GeneralSettings ManageContentDatabases ManageWebAppFeatures ListWebApplications CreateSite DeleteSite SiteUse QuotaDefinition SiteQuota SiteOwners ListSiteCollections WebPartSecurity SelfService WebApplicationSecurity ManagePolicy ManageAuthentication OfficialFile HtmlViewer DocConversion WorkflowManagement FarmServers TopologyServices IncomingEmailServer ApproveDGs EmailConfiguration RunningJobs JobDefinitions AlternateAccessMappings ManageFarmFeatures Solutions ServiceAccount Irm Antivirus BlockedFileTypes AdministrationRoles Backup BackupHistory Restore BackupStatus DiagnosticLogging UsageAnalysis DefaultDatabase DataRetrieval SiteUpgradeStatus FinalizeUpgrade CreateSite HomePage ManageAnalytics PortalSiteUsage PortalWebUsage AddBDCApp BDCApplications BDCEntities MNGPerms BDCProfPage 6a9c4822-504f-42fa-b ExportEventToolbarButton ExportContactToolbarButton ChangeNameDescription ChangeOptionalSettings ChangeWorkflowSettings RemoveContentType AddField ReorderFields ChangeNameDescriptionGroup ChangeOptionalSettings ChangeWorkflowSettings RemoveContentType AddField ReorderFields SiteActionsToolbar DeployManage DeploySettings DeployStatus ChangeDMSettings ChangeDMSettings ExcelServerSettings ExcelServerFileTrust ExcelServerTrustedDcls ExcelServerSafeDataProviders ExcelServerUserDefin ewrViewAsHtmlFromForm ewrViewAsHtmlFromForm ewrViewAsHtmlFromForm ewrViewAsHtmlFromForm ewrViewAsHtmlFromEcb ewrViewAsHtmlFromEcb ewrViewSnapshotInExcel ewrViewSnapshotInExcel FeaturePushdown HoldECBItem IPFSApplicationConfi IPFSApplicationConfi IPFSApplicationConfi IPFSApplicationConfi IPFSApplicationConfi FormServerEcbItemOpenXsn FormServerEcbItemOpe FormServerEcbItemOpe FormServerEcbItemOpe FormServerEcbItemOpe EnableAudienceTargeting SiteDirSettings MasterSiteDirectorySettings SiteDirectoryLinksCheckerJob Migration AreaNavigationSettings SearchServiceManagement configureEnhacedSearch ManageScopes ManageSpecialTerms SearchSettings SspSearchAnalytics ManageSSP ManageInterFarmServices CheckFarmServices SessionState QuiesceFarm LicenseConversion ChangeCTConverterSettings SchedulingLink AreaTemplateSettings CmsMasterPageCatalog AreaWelcomePage AreaCacheSettings SiteCacheSettings SiteCacheProfiles ObjectCacheSettings CreatePublishingPage PublishingSiteAction AreaChromeSettings SiteManagement NoCrawlSettingsPage SiteManagerLogs VariationSettings VariationLabels VariationLogs TranslatableSettingsPage PolicyTemplate ListPolicySettings ContentTypePolicySettings ContentTypeTemplateP AuditSettings PolicyRptConfiguration PolicyFeaturesConfig RelLinksSettings AuditReporting WorkflowReporting PeopleAndGroups SiteCollectionAdministrators User ProjectSettings NavOptions Theme TopNav QuickLaunch SaveAsTemplate ReGhost MasterPageCatalog ManageCType ManageField SiteTemplates ListTemplates WebParts Workflows RegionalSettings LibrariesAndLists WebUsage UserAlerts RSS SrchVis ManageSubWebs ManageSiteFeatures DeleteWeb DeletedItems SiteCollectionUsage Storage ManageSiteCollectionFeatures Hierarchy Portal SkuUpgrade CmsCheckSpellingEditForm CmsCheckSpellingNewForm SingleSignon ManageProf ManagePriv ManagePS TrustedPersLinks ManagePubLinks ManagePersLinks ManagePermissions ManageAud

/> GroupId Location Sequence RegistrationType RegistrationId uCustomizer SiteActions Microsoft.SharePoint.StandardMenu WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 10 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 20 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 30 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 60 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 70 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 80 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 90 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 110 WebApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 120 SiteManagement Microsoft.SharePoint.Administration.ApplicationManagement 10 SiteManagement Microsoft.SharePoint.Administration.ApplicationManagement 20 SiteManagement Microsoft.SharePoint.Administration.ApplicationManagement 40 SiteManagement Microsoft.SharePoint.Administration.ApplicationManagement 50 SiteManagement Microsoft.SharePoint.Administration.ApplicationManagement 60 SiteManagement Microsoft.SharePoint.Administration.ApplicationManagement 70 SiteManagement Microsoft.SharePoint.Administration.ApplicationManagement 80 ApplicationSecurity Microsoft.SharePoint.Administration.ApplicationManagement 10 ApplicationSecurity Microsoft.SharePoint.Administration.ApplicationManagement 20 ApplicationSecurity Microsoft.SharePoint.Administration.ApplicationManagement 30 ApplicationSecurity Microsoft.SharePoint.Administration.ApplicationManagement 40 Providers ApplicationSecurity Microsoft.SharePoint.Administration.ApplicationManagement 50 ExternalService Microsoft.SharePoint.Administration.ApplicationManagement 20 ExternalService Microsoft.SharePoint.Administration.ApplicationManagement 30 ExternalService Microsoft.SharePoint.Administration.ApplicationManagement 40 WorkflowManagement Microsoft.SharePoint.Administration.ApplicationManagement 10 Topology Microsoft.SharePoint.Administration.Operations 10 Topology Microsoft.SharePoint.Administration.Operations 20 Topology Microsoft.SharePoint.Administration.Operations 40 Topology Microsoft.SharePoint.Administration.Operations 50 Topology Microsoft.SharePoint.Administration.Operations 40 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 10 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 20 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 30 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 50 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 60 Security Microsoft.SharePoint.Administration.Operations 10 Security Microsoft.SharePoint.Administration.Operations 15 Security Microsoft.SharePoint.Administration.Operations 20 Security Microsoft.SharePoint.Administration.Operations 30 Security Microsoft.SharePoint.Administration.Operations 40 BackupRestore Microsoft.SharePoint.Administration.Operations 10 BackupRestore Microsoft.SharePoint.Administration.Operations 20 BackupRestore Microsoft.SharePoint.Administration.Operations 30 BackupRestore Microsoft.SharePoint.Administration.Operations 40 LoggingAndReporting Microsoft.SharePoint.Administration.Operations 10 LoggingAndReporting Microsoft.SharePoint.Administration.Operations 20 DataConfiguration Microsoft.SharePoint.Administration.Operations 10 DataConfiguration Microsoft.SharePoint.Administration.Operations 20 Upgrade Microsoft.SharePoint.Administration.Operations 10 Upgrade Microsoft.SharePoint.Administration.Operations 20 Links Microsoft.SharePoint.Administration.ApplicationCreated 10 Links Microsoft.SharePoint.Administration.ApplicationCreated 20 PortalAnalytics Office.Server.ServiceProvider.Administration 10 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 30 SiteAdministration Microsoft.SharePoint.SiteSettings 30 BDC Office.Server.ServiceProvider.Administration 101 BDC Office.Server.ServiceProvider.Administration 102 BDC Office.Server.ServiceProvider.Administration 103 BDC Office.Server.ServiceProvider.Administration 104 BDC Office.Server.ServiceProvider.Administration 105 356-817f821f623b ActionsMenu Microsoft.SharePoint.StandardMenu List 107 DisplayFormToolbar List 106 DisplayFormToolbar List 105 General Microsoft.SharePoint.ContentTypeSettings 10 General Microsoft.SharePoint.ContentTypeSettings 20 General Microsoft.SharePoint.ContentTypeSettings 30 General Microsoft.SharePoint.ContentTypeSettings 100 Fields Microsoft.SharePoint.ContentTypeSettings 10 Fields Microsoft.SharePoint.ContentTypeSettings 20 General Microsoft.SharePoint.ContentTypeTemplateSettings 10 General Microsoft.SharePoint.ContentTypeTemplateSettings 20 General Microsoft.SharePoint.ContentTypeTemplateSettings 40 General Microsoft.SharePoint.ContentTypeTemplateSettings 100 Fields Microsoft.SharePoint.ContentTypeTemplateSettings 10 Fields Microsoft.SharePoint.ContentTypeTemplateSettings 15 Fields Microsoft.SharePoint.ContentTypeTemplateSettings 20 SiteActions Microsoft.SharePoint.StandardMenu 2001 ContentDeployment Microsoft.SharePoint.Administration.Operations 10 ContentDeployment Microsoft.SharePoint.Administration.Operations 20 ContentDeployment Microsoft.SharePoint.Administration.Operations 30 General Microsoft.SharePoint.ContentTypeSettings 100 ContentType 0x0101 General Microsoft.SharePoint.ContentTypeTemplateSettings 100 ContentType 0x0101 ExcelServer Office.Server.ServiceProvider.Administration 51 edLocations ExcelServer Office.Server.ServiceProvider.Administration 52 ExcelServer Office.Server.ServiceProvider.Administration 53 ExcelServer Office.Server.ServiceProvider.Administration 54 edFunctions ExcelServer Office.Server.ServiceProvider.Administration 55 DisplayFormToolbar 2500 FileType xlsx DisplayFormToolbar 2500 FileType xlsb EditFormToolbar 2500 FileType xlsx EditFormToolbar 2500 FileType xlsb EditControlBlock 255 FileType xlsx EditControlBlock 255 FileType xlsb EditControlBlock 256 FileType xlsx EditControlBlock 256 FileType xlsb Upgrade Microsoft.SharePoint.Administration.Operations 70 EditControlBlock 100 ContentType 0x01 gurationManage IPFSApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 10 gurationConfig IPFSApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 20 gurationUpload IPFSApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 30 gurationManageDataConnectionFiles IPFSApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 40 gurationManageFormsServiceProxy IPFSApplicationConfiguration Microsoft.SharePoint.Administration.ApplicationManagement 50 EditControlBlock 255 FileType xsn nInfoPathDocument EditControlBlock 255 ProgId InfoPath.Document nInfoPathDocument2 EditControlBlock 255 ProgId InfoPath.Document.2 nInfoPathDocument3 EditControlBlock 255 ProgId InfoPath.Document.3 nInfoPathDocument4 EditControlBlock 255 ProgId InfoPath.Document.4 GeneralSettings Microsoft.SharePoint.ListEdit 10 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 21 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 21 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 22 Upgrade Microsoft.SharePoint.Administration.Operations 50 Customization Microsoft.SharePoint.SiteSettings 10 SearchGroup Microsoft.SharePoint.Administration.ApplicationManagement 10 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 1 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 2 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 3 Search Office.Server.ServiceProvider.Administration 10 Search Office.Server.ServiceProvider.Administration 30 OfficeServerCoreServices Microsoft.SharePoint.Administration.ApplicationManagement 10 OfficeServerCoreServices Microsoft.SharePoint.Administration.ApplicationManagement 20 OfficeServerCoreServices Microsoft.SharePoint.Administration.ApplicationManagement 30 OfficeServerCoreServices Microsoft.SharePoint.Administration.ApplicationManagement 40 GlobalConfiguration Microsoft.SharePoint.Administration.Operations 50 Upgrade Microsoft.SharePoint.Administration.Operations 80 General Microsoft.SharePoint.ContentTypeTemplateSettings 100 GeneralSettings Microsoft.SharePoint.ListEdit.DocumentLibrary 10 Customization Microsoft.SharePoint.SiteSettings 10 Galleries Microsoft.SharePoint.SiteSettings 100 Customization Microsoft.SharePoint.SiteSettings 10 SiteAdministration Microsoft.SharePoint.SiteSettings 200 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 200 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 200 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 200 WebPages Microsoft.SharePoint.Create 100 sMenuCustomizer SiteActions Microsoft.SharePoint.StandardMenu Customization Microsoft.SharePoint.SiteSettings 10 SiteAdministration Microsoft.SharePoint.SiteSettings 210 Customization Microsoft.SharePoint.SiteSettings 210 SiteAdministration Microsoft.SharePoint.SiteSettings 250 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 210 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 220 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 230 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 230 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 90 Permissions Microsoft.SharePoint.ListEdit 100 General Microsoft.SharePoint.ContentTypeSettings 100 olicySettings General Microsoft.SharePoint.ContentTypeTemplateSettings 100 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 70 LoggingAndReporting Microsoft.SharePoint.Administration.Operations 40 Security Microsoft.SharePoint.Administration.Operations 50 SiteAdministration Microsoft.SharePoint.SiteSettings 100 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 71 LeftNavBarLinks Microsoft.SharePoint.Workflows 100 UsersAndPermissions Microsoft.SharePoint.SiteSettings 10 UsersAndPermissions Microsoft.SharePoint.SiteSettings 20 UsersAndPermissions Microsoft.SharePoint.SiteSettings 40 Customization Microsoft.SharePoint.SiteSettings 10 Customization Microsoft.SharePoint.SiteSettings 20 Customization Microsoft.SharePoint.SiteSettings 30 Customization Microsoft.SharePoint.SiteSettings 40 Customization Microsoft.SharePoint.SiteSettings 50 Customization Microsoft.SharePoint.SiteSettings 60 Customization Microsoft.SharePoint.SiteSettings 80 Galleries Microsoft.SharePoint.SiteSettings 10 Galleries Microsoft.SharePoint.SiteSettings 20 Galleries Microsoft.SharePoint.SiteSettings 30 Galleries Microsoft.SharePoint.SiteSettings 40 Galleries Microsoft.SharePoint.SiteSettings 50 Galleries Microsoft.SharePoint.SiteSettings 60 Galleries Microsoft.SharePoint.SiteSettings 70 SiteAdministration Microsoft.SharePoint.SiteSettings 10 SiteAdministration Microsoft.SharePoint.SiteSettings 20 SiteAdministration Microsoft.SharePoint.SiteSettings 30 SiteAdministration Microsoft.SharePoint.SiteSettings 40 SiteAdministration Microsoft.SharePoint.SiteSettings 60 SiteAdministration Microsoft.SharePoint.SiteSettings 65 SiteAdministration Microsoft.SharePoint.SiteSettings 70 SiteAdministration Microsoft.SharePoint.SiteSettings 80 SiteAdministration Microsoft.SharePoint.SiteSettings 90 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 10 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 30 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 40 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 45 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 50 SiteCollectionAdmin Microsoft.SharePoint.SiteSettings 60 Upgrade Microsoft.SharePoint.Administration.Operations 60 EditFormToolbar 10 ContentType 0x01 NewFormToolbar 10 ContentType 0x01 Security Microsoft.SharePoint.Administration.Operations 50 UAP Office.Server.ServiceProvider.Administration 11 UAP Office.Server.ServiceProvider.Administration 13 UAP Office.Server.ServiceProvider.Administration 14 UAP Office.Server.ServiceProvider.Administration 15 UAP Office.Server.ServiceProvider.Administration 16 UAP Office.Server.ServiceProvider.Administration 17 UAP Office.Server.ServiceProvider.Administration 18 AUD Office.Server.ServiceProvider.Administration 21

Adding CustomMenu to any Group in SharePoint using CustomAction & ControlAssembly

Posted by milap shah

Creating Hierarchical Menus with a CustomAction in SharePoint

It’s a fairly known technique to make use of CustomActions to add elements to the out-of-the-box user interface of SharePoint: you can add menu items to the Site Actions menu, you can add links on the Site Settings page, etc. The following piece of XML is the manifest of a feature that will add a new menu item to the Site Actions menu:

For a more detailed description of CustomActions, I recommend following articles:

Another variation on this technique is to provide a reference to a class, instead of having fixed UI element specified in the XML. The following piece of XML points to the class ListSettingsMenu in the DemoCustomAction assembly.

The cool thing is that you now can write code that will render the UI element; it’s even possible to create a hierarchical menu. The following implementation of the ListSettingsMenu class, in combination with the XML from above, is adding one extra menu item to the Site Actions menu (List Settings). This new menu item will contain a sub menu item for every list on the site, these sub menu items will point to the settings pages of the corresponding lists. The ListSettingsMenu class inherits from the WebControl class, by overriding the CreateChildControls method, you can instantiate SubMenuTemplate and MenuItemTemplate instances, and add them to the Controls collection. An instance of the SubMenuItemTemplate class corresponds with a menu item that contains sub menu items. These sub menu items are instances of the MenuItemTemplate class. By setting the Text, Description and ImageUrl properties of these classes, you can specify how the menu items will be rendered in the SharePoint UI. The ClientOnClickNavigateUrl of the MenuItemTemplate class specifies the URL for the menu item itself.

namespace DemoCustomAction
{
    public class ListSettingsMenu: System.Web.UI.WebControls.WebControl
    {
        protected override void CreateChildControls()
        {
            SubMenuTemplate listSettings = new SubMenuTemplate();
            listSettings.Text = "List Settings";
            listSettings.Description = "Manage settings for lists on this site";
            listSettings.ImageUrl = "/_layouts/images/lg_ICASCX.gif";

            foreach (SPList list in SPContext.Current.Web.Lists)
            {
                if (!list.Hidden)
                {
                    MenuItemTemplate listItem = new MenuItemTemplate();
                    listItem.Text = list.Title;
                    listItem.Description = string.Format(
                        "Manage settings for {0}", list.Title);
                    listItem.ImageUrl = list.ImageUrl;

                    string url = string.Format(
                        "{0}/_layouts/listedit.aspx?List={{{1}}}",
                        SPContext.Current.Web.Url, list.ID.ToString());
                    listItem.ClientOnClickNavigateUrl = url;

                    listSettings.Controls.Add(listItem);
                }
            }

            this.Controls.Add(listSettings);
        }
    }
}

To deploy all of this first of all the assembly (DLL) that contains the ListSettingsMenu should be built and copied either to the Global Assembly Cache or the BIN folder of the SharePoint site where you’d like to use it. Secondly the feature should be installed by copying the feature files and running STSADM -o installfeature -n featurename. Finally a SafeControl element must be added to the web.config, so the ListSettingsMenu control is marked as safe. If you forget the last step, you won’t get an error, but the extra menu item won’t be rendered. Here is a screenshot of the result:

The only caveat for this technique seems to be that you can’t use it to add a hierarchical menu in a EditControlBlock (ECB) CustomAction. The menu items of the ECB are rendered using Javascript. If you want to see a full blown example of what you can accomplish, check out the latest addition to the SmartTools project: the Enhanced Site Actions menu.

StepByStep Site Directory in SharePoint

Posted by milap shah on Sunday, November 1, 2009

Check this link http://www.chandima.net/Blog/archive/2008/08/09/how-do-i-list-all-my-sharepoint-sites-in-the-site-gallery.aspx for step by step instructions for configuring Site Directories.

Choosing between WSS and MOSS

Posted by milap shah

Many clients ask whether they should be using Windows SharePoint Services 3.0 (WSS 3.0) or SharePoint Server 2007. Here is a high level list that I use to help them make this decision.

A high level question to answer is: "Is the organization serious about using SharePoint technologies as part of the tool set that is provided to the end user community." In almost every case where the organization answers "yes" they end up selecting the SP Server 2007 product.

Questions to consider:

Is there budget for the project. WSS 3.0 is free, and no CALs are required, while SP Server 2007 costs money per server, typically uses SQL 2005 servers to store the data, and the CALs cost money. So there is a big delta in cost between the two. The Server version of the product can be evaluated before the commitment is made.
Are My Sites needed? They're only available in the SP Server 2007.
Is a Site Directory needed? The Site Directory feature is only available in the Server 2007 product and can be very helpful if a large number of sites will be created.
Are user profiles needed? the Server version of the product can connect to AD and pull in user information which is then stored in the profiles db.> Is there a need to search and index content sources outside of the SharePoint content dbs? If so SP Server 2007 is needed and it can index file shares, web sites, Exchange Public Folders and other sources out of the box.
Will the organization be using workflows for production processes? WSS 3.0 is very limited in out of the box workflows, while SP Server 2007 offers more flexibility with Approval, Collect Feedback, Collect Signatures and Disposition Approval workflows.
Is integration with MS Information Rights Management (IRM) needed? If so, you need the SP Server 2007 product.
Are retention and auditing policies needed? If so, you need the SP Server 2007 product.
Will the more advanced branding and publishing tools be needed? SP Server 2007 provides master pages and page layouts that can be used to brand the look and feel of the top-level and subsites.
Are policies, auditing and compliance features needed? SP Server 2007 allows for the creation of document retention and expiration policies, workflow processes to define expiration, tacking and auditing and other tools.
Are browser-based forms required? If the Enterprise features are enabled with SP Server 2007, browser based forms can be published (so InfoPath is NOT required to fill out a form).
Will the organization be using Excel Services? This feature is only available in SP Server 2007.
Is the Business Data Catalog required? The Business Data Catalog allows SP to mine data from external databases via application definition files. A number of dedicated web parts then enable SP Server 2007 to display this data to form advanced dashboards.
Is Single Sign-On of interest? Again, this is only available with SP Server 2007.

SharePoint and .Net Fun

Custom PowerShell Commands

Custom stsadm commnad in SharePoint 2007

Create a class that implements ISPStsadmCommand

Register the new class and assembly

Example

Workaround for Double Hop issue

ListFieldIterator Control to render the sharepoint fields the way you want.

Some Important Links

Hide Multiple Upload menu from a Document Library

Add Custom Menus using CustomAction

Using ControlAssembly to Add New Menus to any GroupId

Hiding Menus in SharePoint

Alternatives

Use a Feature.

SharePoint CustomAction Identifiers

Adding CustomMenu to any Group in SharePoint using CustomAction & ControlAssembly

Creating Hierarchical Menus with a CustomAction in SharePoint

StepByStep Site Directory in SharePoint

Choosing between WSS and MOSS

About me

Categories

Text

About Me

Blog Archive