The first step is to create a batch file containing:

SET STSADM=”c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\STSADM.EXE”
%STSADM% -o enumsites -url <Your Site> SiteStats.txt
Pause

Pretty obviously, where it says <Your Site>, you need to change that to the name of the Web application that you need to produce the statistics for.

Next you need to copy the batch file to your Web front-end server and run it.

The output will be in a file called SiteStats.txt. Open the file and for each site collection you will see ‘StorageUsedMB=’ and a value. It’s the value that you’re interested in.

On a completely different topic: on Tuesday 13 September the Virtual CICS user group meets. Rocket Software’s Charles Jones will be discussing “CICS TS 4.2: Leveraging event processing and high-performance Java”. More details about how to register can be found on the user group Web site at fundi.com/virtualcics.

There are a few different parts to custom branding a SharePoint Web application. You will need SharePoint Designer to create and change the pages. You will need to create a new master page and a CSS file to apply to the master page.

SharePoint Designer is a free application that is available from Microsoft at www.microsoft.com/downloads/en/details.aspx?familyid=baa3ad86-bfc1-4bd4-9812-d9e710d44f42&displaylang=en. SharePoint Designer allows you to open your SharePoint Web application to see and access all the component parts and elements of the application. You are able to navigate through the whole site, which will give you a better idea of how a SharePoint application is built. Be carefully not to change anything unless you know what it is – you could break the Web application if you remove or change the wrong thing!

SharePoint Designer also allows the pages and code to be edited, which is good news for someone new to SharePoint because everything is available within one location.

Let’s start with master pages. These are the templates that are applied to all pages on a SharePoint Web application. They are written in ASP.NET 2.0. When applying custom branding to a SharePoint Web application, this is where the majority of the development will be carried out.

CSS (Cascading Style Sheets) are used to style the master page (just like on most Web pages). Within a SharePoint Web application, there is a ‘core.css’ file, which can be found in the ‘_styles’ folder. You won’t be able to navigate here without using SharePoint Designer. This is used by all of the master pages that come by default in a Web application. This file should not be changed. It is best practice to create a bespoke .css file and use this to override the core.css. This means that you will not affect the default master page styles that are used by other pages.

Content PlaceHolders Controls are regions of content on a master page that are predefined but customizable within SharePoint. So, for example, the PlaceHolder is in red, which is housed within an HTML table:

<!– Search Start–>
  <table border=”0″ cellpadding=0 cellspacing=0 width=”100%” class=”customcss.class” >
    <tr>
      <td>

     <asp:ContentPlaceHolder id=”PlaceHolderSearchArea” runat=”server”>
      <SharePoint:DelegateControl runat=”server” ControlId=”SmallSearchInputBox”/>
      </asp:ContentPlaceHolder>

      </td>
    </tr>
  </table>
<!– Search End –>

This is an example of a table that will contain the search placeholder shown below:

Any images that are referenced from within the master page must be able to be viewed by all users. Otherwise, users will be asked to log-in every time they refresh the page if the don’t have permission to the library where the image is stored.

I would suggest creating a folder for your master page within the ‘http://Your App/Style%20Library/images’ and locating all of the images there. This will use the standard image locations from the master pages, but keep them separate so that they can be identified easily during future development or maintenance.

When you’re ready to import branding into a Web application, you need to use the following guidelines.

To import a master page:

1. In SharePoint Designer open up your Web application
2. Navigate to http://your site/_catalogs/masterpage
3. Click File
4. Click Import
5. Add your master page here.

To import an image:

1. In SharePoint Designer open up your Web application
2. Navigate to http://your site/Images
3. Click File
4. Click Import
5. Add your image here.

To import a CSS file:

1. In SharePoint Designer open up your Web application
2. Navigate to http://your site/_styles
3. Click File
4. Click Import
5. Add your CSS file here.

Good luck with your modifying your branding.

The first thing to do when creating a custom Web Part is to set up a development environment. You need to create a development SharePoint 2007 (SP2007) server and give it a name. For SharePoint 2007 you need Visual Studio 2008 (VS2008). It’s worth noting that you can’t use Visual Studio 2010 (VS2010).

Install VS2008 onto your development SP2007 server. Next install the VS2008 SharePoint plug-in called “VSeWSSv13_AMD64_Build-433.exe”. This can be found at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=fb9d4b85-da2a-432e-91fb-d505199c49f6. This plug-in adds the Web Part project to VS2008. Once this is in place, you’ll be able to actually create a custom Web Part.

Open VS2008, then click ‘File/New/Project’. Find the ‘Visual C#’ list and expand that. Next click ‘SharePoint’, and in the right-hand box click ‘Web Part’. Give your new project a name. The naming convention is og.wp.%Name%, where:
og = your organization (abbreviated, eg use gs if you’re company is called ‘Great Shoes’, etc.)
wp = Web Part
.%Name% = the name of the Web Part.

Make sure you tick ‘Create directory for solution’ – see Figure below.

Click picture for larger version

Next you’ll see a trust level box. Make sure that it looks like this:

Click picture for larger version

And click ‘OK’.

You can now go ahead and write your Web Part using Visual C#.

The next stage shouldn’t be missed – it’s testing your custom Web Part. You need to tell VS2008 where to deploy the Web Part. Click ‘Project’, ‘%PROJECT NAME% Properties’. On the tabs click ‘Debug’ and change the ‘Start browsers with URL’ box to point to your test site, eg http://yourdevelopmentserver:5003/. Click the cross in the right hand corner to save the changes.

To deploy your Web Part, click ‘Build’, ‘Deploy %PROJECT NAME%’. This will add the solution to SharePoint central admin and deploy the solution to your test site. You can add your Web Part to your test site in the same way that you would add any other Web Parts, and now you can test it.

It’s useful to know how to retract a test Web Part. Open your project in VS2008, click ‘Build’ and then ‘Retract Solution’. This will retract the solution from your test site and remove it from SharePoint central admin. You now need to manually remove the pointer from your test site. To do this open your test site and click ‘Site Actions/Site Settings/Modify All Site Settings’. Under Galleries click ‘Web Parts’ and delete your development Web Part.

Assuming that your Web Part worked as planned (finally!), you’ll want to deploy your solution into your live environment. Firstly, locate your project, eg ‘C:\Users\%USERNAME%\Documents\Visual Studio 2008\Projects’, then double-click on your new project, and locate the debug folder. Within this you should find %PROJECT NAME%.wsp. Finally copy this .wsp file onto your Live SharePoint Server.

I’ll share Darren’s full instructions for installing a solution another time.

Cloud computing marks a major shift for information technology managers. Users don’t load software onto their computers but instead access programs via the Web. It’s a way to cut the cost of managing on-site computer resources. READ MORE