SharePoint: How to display blog feed using XML Web Part?

There is no RSS Viewer web part in Windows SharePoint Services 3.0 and my client wanted to show list feed on our intranet homepage. The constraint was, not to use some third-party Web Parts. Searching around the net, I found out that the XML Web Part is practically the same thing. After all, what’s an RSS feed other than an XML file? Getting a little creative, I thought of other ways to simply retrieve the content from other lists.

My solution? XML Web Part

Here's my list feed example as easy step-by-step guide.

1).Move to SharePoint page you want to add your list feed.

2).Open this page in edit view and add new Web Part called XML Web Part.

3).If Web Part is added to page then open it's settings window.

4).On the field XML Link insert your list feed URL. Check out if link is correct and content is receivable by clicking the link titled as Test Link.

5).Push button titled as [XSL Editor].

6).XSL editing window is opened and now insert XSL code given below. When inserted click [OK].

7).If everything is okay then you should see your list's titles as bulleted list and then save edited page.

XSL you need is here. Take it using copy and paste.

'<'?xml version="1.0" encoding="UTF-8"?'>'

'<'xsl:stylesheet version="1.0" xmlns:xsl="" exclude-result-prefixes="xsl"'>'

'<'xsl:output method="xml" omit-xml-declaration="yes" indent="yes"/'>'

' <'xsl:template match="/"'>'

' <'div'>'

'<'xsl:apply-templates select="rss/channel"/'>'



'<'xsl:template match="rss/channel"'>'

'<'xsl:variable name="link" select="link"/'>'

'<'xsl:variable name="description" select="description"/'>'


'<'xsl:apply-templates select="item"/'>'



'<'xsl:template match="item"'>'

'<'xsl:variable name="item_link" select="link"/'>'

'<'xsl:variable name="item_title" select="description"/'>'


'<'a href="{$item_link}" title="{$item_title}" '>'

'<'xsl:value-of select="title"/'>'





Note : There is a security issue in the above post. Please set the “Anonymous Access” for the site to "entire site".

  • NOTE : "There is a security issue",We need to enable the Anonymous Access for the site collection,only then we are able to see the result.

    Server Hardware Sizer for MOSS

    The HP ProLiant Sizer for Microsoft Office SharePoint Server 2007 is an automated tool that provides a quick and consistent methodology to determine a "best-fit" server for your individual needs and enables you to both quickly compare different solution configuration (what-if scenario) and also to obtain a highly detailed, customizable server and storage solution complete with bill of materials and pricing.

    Kodak Scanners adds Sharepoint Button

    March 17, 2009: Kodak has added direct scanning to Microsoft Sharepoint Server tor the KODAK i1200 and i1300 Series Scanners.

    “Business use of MICROSOFT SHAREPOINT Server to share and store documents has exploded during the past year. Kodak recognizes the importance of this and rises to the challenge, providing customers easy scanner uploads to SHAREPOINT Servers with a just a press of the scanner’s button,” said Tony Barbeau, Vice President, Marketing, Document Imaging, Business Solutions and Services, Eastman Kodak Company.

    “Entering paper content to MICROSOFT SHAREPOINT repositories has never been so easy.”

    The MICROSFT SHAREPOINT Server connection is totally automated, requiring no additional server components and featuring a new status utility program allows users to scan and upload images simultaneously. Smart Touch enhancements also include bitmap image output, single page PDF output and customized shortcuts.

    Other new features include:

    * improved identification and deletion of blank pages;

    * merging front and rear images;`and

    * capability for third party applications to initiate scans via the Smart Touch feature, passing the image back to an application.

    For power users, KODAK Capture Pro Software, available separately, offers an even richer button function that also supports batch separation, complex file indexing and many other production quality features.

    via idm

    BLOB Caching : Boost Performance

    A typical sharepoint site refers multiple CSS, JS and Image files. Other than the page itself, if we can add non-zero directive to the rest of items, then we can reduce the server round trips and in a way can improve the performance. It's not at all complex to turn on disk based caching in Sharepoint (BLOB Caching). Simply find the following line in web.config

    BlobCache location="C:\blobcache" path="\.(gif¦jpg¦png¦css¦js)$ " maxSize="10" enabled="false" />

    and set enabled="true" from enabled="false"

    Location : Physical Location of the temporary files

    Path : Filter for files (extension) to be included in process

    MaxSize : Max. Size in GBs for the files to be stored on file system

    additionaly we can set one more property

    Max-age : (seconds) The amount of time in seconds that items should be cached on the client computer.

    By setting the max-age attribute to a non-zero value, items have a expiration value associated with them and the browser no longer needs to download the item or verify if it has the latest version.

    On a side note, following points should also be kept in consideration with BLOB caching

    • All front end web serves should have the BLOB caching enabled with same configuration
    • BLOB Caching works only for items in Sharepoint libraries
    • Changes in CSS, JS etc, might not reflect immediately. If such a case occurs then the option is to flush the cache by navigating to the site collection's Site Settings. Select "Site Collection Object Cache" and then click "Force this server to reset its disk based cache."

    Why/How of creating Application Pages in Windows SharePoint Services 3.0

    According to Ted Pattison in his book :"You can create custom application pages to add user interface components to a custom solution based on Microsoft Windows SharePoint Services 3.0. Unlike site pages (for example, default.aspx), a custom application page is deployed once per Web server and cannot be customized on a site-by-site basis. Application pages are based in the virtual _layouts directory. In addition, they are compiled into a single assembly DLL. They are also used across all sites within a server farm. For these reasons, they perform better than site pages. With application pages, you can also add inline code. With site pages, you cannot add inline code."
    There couldn't have been a easier way to explain application pages in sharepoint. Creating one is as simple thanks to all mighty MSDN

    Typically, you link custom application pages to application.master, the master page file that is used by the default application pages in Windows SharePoint Services. You should also write application pages to inherit from a base class defined inside the Microsoft.SharePointassembly named LayoutsPageBase. The following example provides the basic layout for a custom application page.

      Site Title: 
      Site ID: 
       Hello World
       The Quintessential 'Hello World' of Application Page

    Note that although you can deploy your application pages directly inside the \LAYOUTS directory, doing so can create file name conflicts between your application pages and those application pages that are created by Microsoft and other companies. It is a best practice to deploy your application pages inside a company-specific or project-specific directory that is nested with the \LAYOUTS directory. For example, you can deploy application pages within a company-specific directory located at the path \LAYOUTS\Litware.
     Read It
    You usually create custom application pages with a link to the application.master file. The custom application page demonstrated in this How-To sample adds three Content tags to add HTML content to the resulting page. In particular, this page replaces three placeholders that are defined inside application.master:PlaceHolderMainPlaceHolderPageTitle andPlaceHolderPageTitleInTitleArea. However, these are only three of the many different placeholders that you can choose to replace.
    Also note that an application page can have a script block at the top with code that programs against the object model. When you program a similar page within Microsoft Visual Studio 2005, you can benefit from conveniences such as color-coding and Microsoft IntelliSense. However, you must add the correct @Assembly directive to the top of the page to reference the Microsoft.SharePoint assembly.
    Application pages are useful because they provide quick and easy access to the Windows SharePoint Services object model. After you create an application page and provide an overridden implementation of the OnLoad method, you can obtain entry points into the Windows SharePoint Services object model in a site-specific context by using the following code.
    SPSite siteCollection = SPContext.Current.Site;
    SPWeb site = SPContext.Current.Web;
    Visual Basic
    Dim siteCollection As SPSite = SPContext.Current.Site
    Dim site As SPWeb = SPContext.Current.Web
    The ability to obtain site-relative context makes writing application pages far more powerful. An application page can function differently depending on which site you go through to access it. When you navigate to an application through the context of one site, it typically appears and functions differently than when you navigate to it through the context of another site.