Adding links to View Selectors through SharePoint Features

Using Features makes it easy to add actions to menus of the user interface in SharePoint. To define a custom action for a particular menu, you must identify the menu by setting the location to the appropriate SharePoint namespace, and by using the ID that SharePoint uses to identify the specific location. The following example shows how to add a link to to the a view selector through a Feature.

<CustomAction
    Id="custom.ActionMenu"
    Location="Microsoft.SharePoint.StandardMenu"
    GroupId="ViewSelectorMenu"
    Title="XSLT View"
    RegistrationType="List"
    RegistrationId="101"

  >
<UrlAction Url="xsltdataviewurl.aspx"/>
</CustomAction>
Advertisements

Your Very Own Permissions Dashboard by Laura Rogers

Using a web service and a little magic, it’s possible to create your own data view web part “dashboard” to quickly get to permissions and other screens for all of the lists and libraries on your SharePoint site.  Here’s an example of what the goal is:

 

This is really a Very cool read for SharePoint! Lot of folks asking how to do this and Laura Rogers has done a fantastic job showing you how. Here is a link to the full article !

Programming against IIS Application pools in SharePoint

Earlier versions of SharePoint did make some use of the .NET Framework, but SharePoint 2007 has been rebuilt from ground up on top of it, meaning SharePoint applications are in fact tremendously powerful ASP.NET applications.

What are Application Pools?
A classic example that I always utilize to discuss application pools is a web hosting company that hosts many websites on a common server, and therefore all the websites hosted on this server share the system resources. If one of the hosted websites had a memory leak, this potentially takes memory away from the other hosted sites, causing errors and inconveniences.
Prior to IIS 6.0, at least, that was the case. Too many server resources were shared between websites, and it was too easy for an error to creep in and damage the entire server process.

Fortunately, IIS 6.0 introduced a new concept called application pools. Application pools form boundaries around applications, separating them from each other even though they are being hosted on the same server.

Each application pool is given its own set of server resources (including memory). That way, the hosting company can now host each website in its own application pool to accomplish security, reliability, and availability and to prevent the leaky or misbehaving site from affecting other sites.

Application Pools in SharePoint Object Model

The SharePoint OM comprises types whose instances correspond to IIS entities such as application pools, web sites,…. These types permit you to program against these entities within your code

SharePoint represents each IIS application pool with an instance of a type named SPApplicationPool, which allows you to program against IIS application pools from your managed code. Here are some of the public methods of the SPApplicationPool class that you can use in your managed code:

  • Provision. This method creates the application pool.
  • Unprovision. This method removes the application pool.
  • Update. This method updates and commits the changes made to the application pool.
  • UpdateCredentials. This method updates and commits the credentials under which the
    application pool is running.
   1:  SPWebServiceCollection wsc = new SPWebServiceCollection(SPFarm.Local);
   2:  foreach (SPWebService ws in wsc)
   3:  {
   4:       SPApplicationPoolCollection appPoolCollection= ws.ApplicationPools;
   5:       foreach (SPApplicationPool appPool in appPoolCollection)
   6:       {
   7:           // Your code
   8:       }
   9:  }