SharePoint 2007 Features - Release: 2.0 Production

 

Downloads & Files

Content Type Hierarchy Feature (separate download)

application, 2K, uploaded Mar 22 2007  - 2542 downloads

Log Viewer Feature (separate download)

application, 4K, uploaded Mar 22 2007  - 6704 downloads

Manage Form Users Feature (separate download)

application, 13K, uploaded Aug 31 2007  - 1936 downloads

Presence Contact List Feature (separate download)

application, 12K, uploaded Mar 22 2007  - 1545 downloads

Placeholder Master Feature (separate download)

application, 9K, uploaded Jan 8 2008  - 1226 downloads

Print List Feature (separate download)

application, 7K, uploaded Mar 22 2007  - 3956 downloads

Task Alert Feature (separate download)

application, 6K, uploaded Jan 24 2008  - 1730 downloads

Task Mover Feature (separate download)

application, 4K, uploaded Mar 11 2008  - 1258 downloads

Theme Changer Feature (separate download)

application, 4K, uploaded Mar 22 2007  - 2735 downloads

Debugger Feature (separate download)

application, 2K, uploaded Mar 23 2007  - 3106 downloads

Window Links Feature (separate download)

application, 11K, uploaded May 24 2007  - 3364 downloads

Debug Config Feature (separate download)

application, 8K, uploaded Aug 17 2007  - 1019 downloads

Manage Configuration Modifications (separate download)

application, 9K, uploaded Oct 31 2007  - 892 downloads

Ajax Config Feature (separate download)

application, 9K, uploaded Apr 30 2008  - 3052 downloads

Manage Layouts Site Map Feature (separate download)

application, 12K, uploaded Nov 2 2007  - 547 downloads

Minimal Master (separate download)

application, 5K, uploaded Jan 8 2008  - 880 downloads

Minimal Publishing Site (separate download)

application, 25K, uploaded Nov 2 2007  - 1079 downloads

Manage Hierarchical Object Store Feature

application, 12K, uploaded Nov 7 2007  - 492 downloads

Reset Theme Feature (separate download)

application, 6K, uploaded Sep 2 2008  - 615 downloads

Toolbar Manager (separate download)

application, 7K, uploaded Feb 27 2008  - 2847 downloads

Unique Column Policy Feature (separate download)

application, 16K, uploaded Mar 3 2008  - 1631 downloads

Global Web.Config Feature (separate download)

application, 8K, uploaded Apr 6 2008  - 788 downloads

3.5 Web.Config Feature (separate download)

application, 11K, uploaded Apr 30 2008  - 1612 downloads

Regular Expression Validator (separate download)

application, 6K, uploaded Jun 11 2008  - 429 downloads

SharePoint Events Manager (separate download)

application, 12K, uploaded Jul 15 2008  - 553 downloads

Clean Web Part Error Feature (separate download)

application, 6K, uploaded Sep 2 2008  - 275 downloads

Anonymous Audience Feature (separate download)

application, 5K, uploaded Sep 22 2008  - 269 downloads

Variation Labels Field (separate download)

application, 15K, uploaded Sep 22 2008  - 202 downloads

Custom Application Configuration (separate download)

application, 6K, uploaded Dec 9 2008  - 174 downloads

Create Site in Content DB (separate download)

application, 11K, uploaded Dec 9 2008  - 184 downloads

Source Code for All Features

source code, 11178K, uploaded Dec 9 2008  - 2188 downloads

Documentation for All Features

documentation, 766K, uploaded Dec 9 2008  - 3305 downloads

All Features in a Single Download

SharePoint 2007 Features - Release: 2.0 Production

Mark Arend : Using Reflector to See SharePoint's "Source" Code

 

Do you sometimes use a "reflector" program to examine SharePoint source code? This can be necessary to:

• Understand out how SharePoint is doing something, to find what elements can be customized.
• Understand what members to override in classes you create that inherit from SharePoint classes.

The de facto standard program for doing this is Lutz Roeder's Reflector. The MSDN article on ten must-have tools has a great description of how helpful it can be and how to use it.

One thing the article doesn't tell you is where to find SharePoint's assemblies; fortunately it's not that hard. Click "Open" in Reflector, then with a little bit of browsing, most people easily find the dlls in the ISAPI directory of the "12-hive" (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI).

Mark Arend : Using Reflector to See SharePoint's "Source" Code

Cum Grano Salis

 

OverGen is a tool I wrote that will take an assembly and find all methods in it that are optional and then generate overloads for all those methods that will allow the user to pass in a smaller amount of parameters. For each optional parameter a method has, an extension method will be generated.

Extension Methods are basically a very simple compiler construct that allows a class to extend another class by way of adding methods to it - the extension is very superficial - no methods are actually added to the class but rather, the compiler knows that when such a method is called on class, it will try and find it in supporting classes.

Cum Grano Salis

Notice the "this" keyword on the first parameter? That's what makes this method an extension method. If you did not have this guy, this is what ANY call to .Open would have to look like, even if you only use the first parameter:

app.Workbooks.Open("c:\\temp\\file.xlsx", Type.Missing, Type.Missing,

Type.Missing, Type.Missing, Type.Missing, Type.Missing,

Type.Missing, Type.Missing, Type.Missing, Type.Missing,

Type.Missing, Type.Missing, Type.Missing, Type.Missing);

And here's what the code looks like if you are using the extension method shown above:

app.Workbooks.Open("c:\\temp\\file.xlsx");

How to: Create a Minimal Master Page

Starting from scratch in Sharepoint, in 64 lines of code or less.

Whatever happened to <html></html>?

Creating and completing a master page to begin your SharePoint site customization takes planning and time. If you can, you want to prevent having to rewrite or back out code you don't need in your master page. This topic shows you how to create a minimal master page that includes only the minimal functionality that Office SharePoint Server 2007 requires so that you have a stable platform upon which to build your own master pages. Creating a minimal master page can help you avoid the time-consuming process of backing code out of a pre-existing .master page such as BlueBand.master, or removing functionality and then building it back in when your customization needs change again.

How to: Create a Minimal Master Page

The actual page code for your “minimal” template below.

 

<%-- Identifies this page as a .master page written in Microsoft Visual C# and registers tag prefixes, namespaces, assemblies, and controls. --%>
<%@ Master language="C#" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>
<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>
<%@ Register TagPrefix="PublishingVariations" TagName="VariationsLabelMenu" src="~/_controltemplates/VariationsLabelMenu.ascx" %>
<%@ Register Tagprefix="PublishingConsole" TagName="Console" src="~/_controltemplates/PublishingConsole.ascx" %>
<%@ Register TagPrefix="PublishingSiteAction" TagName="SiteActionMenu" src="~/_controltemplates/PublishingActionMenu.ascx" %>
<%-- Uses the Microsoft Office namespace and schema. --%>
<html>
  <WebPartPages:SPWebPartManager runat="server"/>
  <SharePoint:RobotsMetaTag runat="server"/>

  <%-- The head section includes a content placeholder for the page title and links to CSS and ECMAScript (JScript, JavaScript) files that run on the server. --%>
  <head runat="server">
    <asp:ContentPlaceHolder runat="server" id="head">
      <title>
        <asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server" />
      </title>
    </asp:ContentPlaceHolder>
    <Sharepoint:CssLink runat="server"/>
    <asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server" />
  </head>
  <%-- When loading the body of the .master page, SharePoint Server 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. --%>
  <body onload="javascript:_spBodyOnLoadWrapper();">
    <%-- The SPWebPartManager manages all of the Web part controls, functionality, and events that occur on a Web page. --%>
    <form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
      <wssuc:Welcome id="explitLogout" runat="server"/>
      <PublishingSiteAction:SiteActionMenu runat="server"/> 
      <PublishingWebControls:AuthoringContainer id="authoringcontrols" runat="server">
        <PublishingConsole:Console runat="server" />
      </PublishingWebControls:AuthoringContainer>
      <%-- The PlaceHolderMain content placeholder defines where to place the page content for all the content from the page layout. The page layout can overwrite any content placeholder from the master page. Example: The PlaceHolderLeftNavBar can overwrite the left navigation bar. --%>
      <asp:ContentPlaceHolder id="PlaceHolderMain" runat="server" />
        <asp:Panel visible="false" runat="server">
        <%-- These ContentPlaceHolders ensure all default SharePoint Server pages render with this master page. If the system master page is set to any default master page, the only content placeholders required are those that are overridden by your page layouts. --%>
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea"  runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyRightMargin" runat="server" />
</asp:Panel>
    </form>
  </body>
</html>