It has some reasons for disabling those controls, maybe

• The user doesn’t had the permissions to accesss that control,
• That functionality doesn’t applied for currently selected objects.

On those situations, the ribbon controls are disabled, but visible to users. Instead of diabling, how we can hide those controls. We have option with css styles.

The class name “.ms-cui-disabled” used to represt the in-active ribbon controls. So can just use the following style to hide the ribbon controls. 

We have to apply that style in css page or add within the head tag of SharePoint masterpage.

SPListItem.Update() used to update all the values in SharePoint List Item including pre-defined hidden fields. If we modified the item, that will affects the Modified Date, Modified By, Version information fields.

SPList olist = oweb.Lists.TryGetList(“ListName”);
SPListItem olistitem = olist.Items[1];
olistitem.Title = “Sample List Item”
olistitem.Update();
olist.Update();

SPListItem.SystemUpdate() method used to update the values of the listitem without modifying the Modified Date, Modified By and Version information fields.

SPList olist = oweb.Lists.TryGetList(“ListName”);
SPListItem olistitem = olist.Items[1];
olistitem.Title = “Sample List Item”
olistitem.SystemUpdate();
olist.Update();

But SharePoint 2010 provides the option to restore the default.aspx and List/Library view pages. After deletion , the pages are moved to recyle bin. By using recycle bin, we can restore those pages to the Site.

Content Scheduling was avaialble only the following conditions are true,

1. Content Approval was Enabled on Versioning Settings

2. Create major and minor (draft) versions was set to Document Version History option.

• .Net Managed Application
• Silverlight Application
• ECMA Script

These API’s are much easier to use than already exsiting WebServices.
The recomended Client API was .Net Managed Application than WebServices.

For Default Server Ribbon Customization Locations, browse to  http://msdn.microsoft.com/en-us/library/ee537543.aspx .

Locations for SharePoint Server Ribbon’s Document Tab,

On Coming posts, I’ll add the Locations for Other Tabs and Groups. So Stay tuned.

We are going to use the Feature files to hide the SharePoint 2010. First we will create a Feature file and then we’ll create a element file.

Feature.xml

<?xml version="1.0" encoding="utf-8"?>
<Feature xmlns="http://schemas.microsoft.com/sharepoint/"
    Description="Remove the Button from Server Ribbon"
    Id="5469fb99-2665-46f6-b659-bf6a0117a854"
    Scope="Web"
    Title="Hide Ribbon Button">
  <ElementManifests>
    <ElementManifest Location="Elements.xml" />
  </ElementManifests>
</Feature>

Elements.xml

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <HideCustomAction 
      HideActionId = "<Location ID of Button>"
      Id = "<Id>"
      Location = "<Button Parent Location ID>">
  </HideCustomAction>
</Elements>

There was a HideCustomAction element used to hide / remove the button from Server Ribbon Control. If we want to remove particular Button / Group / Tab we have to specify the respective Button’s Location ID on HideActionId attribute.

HideActionId – Specifies the Location ID of the custom action to hide

Location – Specifies the Parent location Id of the custom action to hide.

By using HideCustomAction, we can hide / remove the Button, Group, Tab.

Example

For example I have provided a element.xml for hiding the Upload Multiple button from the Document Library.

Elements.xml

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <HideCustomAction 
      HideActionId = "Ribbon.Documents.New.AddDocument.Menu.Upload.UploadMultiple"
      Id = "RemoveRibbonUploadMultiple"
      Location = "CommandUI.Ribbon">
  </HideCustomAction>
</Elements>

The above xml file, used to remove the Upload Multiple Documents from the Server ribbon on Document Libraries.

I have added the code in codplex, http://iotapsp.codeplex.com/

In SharePoint 2010, the physical path leads to C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14 instead of folder 12.

New folders available in SharePoint Hive folder are,

• Policy
• UserCode
• WebClients
• WebServices

To Install feature,

PS> Install -SPFeature <FeatureFolderName>

To activate the feature for the site,

PS> Enable -SPFeature <FeatureFolderName> -Url http://server/subsite

Cheers, Stay tuned for the next “What’s New Feature“….

In previous versions; by out of the box, alerts are send only through e-mails, but in SP2010 we can able to send an alerts to mobile devices as SMS Message. For that, we have a new property under SPAlert, that indicates whether the alert is delivered as E-mail or as an SMS Message.

By default alerts can be send only through e-mail. But we can change that default setting by using the new DeliveryChannels Property of SPAlert class. This DeliveryChannels property, specifies the delivery method of the alert.

The following snippet used to set the SMS delivery method to the Alert.

oAlert.DeliveryChannels = SPAlertDeliveryChannels.Sms;

SPAlertDeliveryChannels is the enumerated member, which specifies the method of delivering alerts.

The following example code used to update the sms delivery method to all the alerts for every user available in Current website.

SPWeb oWebsite = SPContext.Current.Web;
SPUserCollection collUsers = oWebsite.Users;

    foreach (SPUser oUser in collUsers)
    {
        SPAlertCollection collAlerts = oUser.Alerts;

         foreach (SPAlert oAlert in collAlerts)
         {
             oAlert.DeliveryChannels = SPAlertDeliveryChannels.Sms;
             oAlert.Update();
         }
     }

That’s all for now!! By soon I’ll be back with the post on new feature in SharePoint 2010.