The circle of life – ** .Net – Training – MOSS **

  • Past Post

  • Vistor Locations

  • Advertisements

Archive for the ‘MOSS 2007’ Category

SharePoint Designer Training

Posted by Clayton James on October 14, 2009

I am currently up in the sugar capital of Australia, Mackay delivering a 3 day SharePoint designer training course.

Lots of cool things learned:

  • Embedding/displaying videos from a document library in a web page
  • Branding: Custom master page design, CSS and overriding core.css
  • Integrate Twitter into your site
  • DataView Web Part: integration with databases, web services and rss (and sharepoint rollups)
  • IE Developer Toolbar is your best friend

And why are those Fab 40 templates so crap!


Posted in MOSS 2007, Presentaitons | Leave a Comment »

User Group Presentation – Content Query Web Part – Part 2

Posted by Clayton James on May 20, 2009

I completed my Part 2 presentation on the CQWP today. I thought that the rain may have kept the numbers down so it was great to see a good turn out.

Topic Covered:

  • How and where best to use – plan ahead
  • Displaying extra columns in result set
  • Modifying the ItemStyle.xsl and .webpart files
  • XSLT
  • Tips and tricks – (thanks Tim for the select=.) tip
  • Subclassing using Visual Studio
  • Deployment


I always need more time presenting at user groups.

Slide deck and demos will be uploaded to the BSPUG site soon.

Posted in MOSS 2007, Presentaitons | 1 Comment »

SharePoint Authentication: FireFoxs works but IE doesn’t

Posted by Clayton James on May 20, 2009

I was having a great deal of pain on a new SharePoint development server recently. Environment = Windows 2008, IE7.


  1. Create a SharePoint web application with a host header on port 80. Create a site collection
  2. Update host file (or DNS) with new host header entry
  3. In IE make sure the web application is in the Intranet Zone
  4. Open up browser in IE navigate to site using host header and the authentication dialog login is displayed.
  5. Enter my credentials 3 times and receive a 401.1 and an entry in the Security Event log
  6. If I open FireFox and browse to the web site the authentication dialog is displayed
  7. I enter my credentials and I can log in fine
    Note: To get rid of the authentication prompt in FireFox
    1. Open FireFox and in the address type about:config
    2. Find the entry network.automatic-ntlm-auth.trusted-uris
    3. Set the Key’s value to a comma seperated list of trusted URIs i.e your host header
  8. So FireFox is fine but IE is having issues



I finally stumbled across a blog article from Brian Farnhill and Ishai Sagi that lead me to the solution.

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6

In my case I am using IE 7 and while the Solution/Workaround discusses two separate methods and states that method one is preferred, I could only fix my issue upon completing method 2

Posted in MOSS 2007, Office 12, WSS 3.0 | 3 Comments »

Importing AD Employee Photos into SharePoint User Profiles

Posted by Clayton James on May 8, 2009

I was recently asked to provide a process for importing Employee pictures into SharePoint so they would show up in search results and various OOTB web parts. This particular client has MOSS but doesn’t use My Sites.

This post by Henry initially helped me out.

They didn’t want the individual users to have the abilty to upload their own photo’s or modify them in any way, this was to be managed by IT.

  1. Create a Picture Library in your Intranet. This will store the photo’s for each employee. When storing employee photo’s chose the filename carefully if you want to populate the AD using scripts. I use something like cjames.jpg which is a correlation to the users account name.
  2. In Active Directory choose an AD property that will be mapped to your SharePoint User Profile Property. In my case I selected the extensionAttribute1 field that is located in the ExchangedAdvanced tab ((note this field may not show up if the Exchange Mgt Console hasn’t been installed)
  3. Populate this field with the URL to the employee’s photo that is in the Picture Library e.g http://sitename/ProfilePhotos/CJames.jpg (look below for a script example)
  4. In SharePoint SSP click the User Profiles and Properties link
  5. Click the View Profile Properties under the heading User Profile Properties
  6. Find the Picture property and select the Edit menu item
  7. Make note of the Usage: Number of profiles using this property. This should increase after we complete a full import
  8. At the bottom of the screen make sure Master Connection is selected and in the Datasource field to map select extensionAttribute1 (note: this field may not show up if the Exchange Mgt Console hasn’t been installed)
  9. Click Ok
  10. Complete a StartFull Import
  11. Once the full import is complete go back into the the Picture property and again check the Usage:Number of profiles that use this property. This should now contain some values.
  12. Verify this by viewing an Employee’s profile and the Picture property

Some things I had issues with:

  • Make sure your Import Connection service account has “Manage User Profile” permissions
  • May need to execute a Full Search crawl once photos are uploaded in the Picture Library

I also wrote a script to populate the AD extensionAttribute1 field as there were over 1000 employee’s and no one put their hand up for this job. The import thing here was for employee photo images to have a one to one mapping with their login account name (samaccountname). The person who runs this script also needs certain permissions in AD to update AD accounts. I would initially comment out the¬†On Error Resume Next so you see if your account has enough privleges or not.

The script is very limited but hopefully it may provide some insight.

‘On Error Resume Next
Set objParent = GetObject(“LDAP://OU=Users,OU=Austraila,OU=Offices,OU=AU,DC=domain,DC=local“)
objparent.Filter = Array(“user”)
for each objUser in objParent
¬† Wscript.Echo “Modifying ” & objUser.Get(“samaccountname”)¬†
¬† objUser.put “extensionAttribute1”, “http://sitename/ProfilePhotos/” & objUser.Get(“samaccountname”) & “.jpg”

Wscript.Echo “End”

Now, IT¬†are responsible whenever they create a new account they must also populate the extensionAttribute1 field with the URL of the picture library and the employee’s picture filename will always be their account name.

Posted in MOSS 2007, Office 12 | 207 Comments »

Tech.Ed 2008…that’s a wrap

Posted by Clayton James on September 7, 2008

It has been a big week!

I taught a two day pre-conference course for Microsoft on building Internet sites using the SharePoint platform. We covered many areas including:

  • Architecture
  • Custom master pages, page layouts, css
  • Web parts
  • Optimisiation. IIS compression, caching, loading core.js
  • Content deployment
  • Extending publishing sites

It was a great couple of days that was also extremely busy with 34 students.

I went to a lot of SharePoint sessions this year and met some leaders in the industry. Todd Bleeker, Ishai Sagi, Ben Curry, Andrew Coates, Joel Olsen .

Todd pioneered SharePoint development by writing the first WSS 3.0 development book (it is my favourite SharePoint development book).

I also went to a Silverlight session. It seemed more a designers sessions than a coders session and I wasn’t really impressed. It demonstrated the expression suite. It is only beta 2 but stills seems lacking in VS integration (I don’t want another product to develop applications) and controls. Lots of hand coding in xaml.

And guess what happened this year…..we didn’t have to wait and get scanned in before sessions. That’s right…we had RFID chips which scanned us into rooms automatically. Great work was completed by the Breeze team in coordinating and brining this to reality.

Posted in .NET 2.0, MOSS 2007, WSS 3.0 | 1 Comment »

Enable Content Scheduling – Collaboration Portal

Posted by Clayton James on August 13, 2008

The Collaboration Portal template doesn’t allow for content scheduling by default. You have to complete a few actions first.

If you are using the Collaboration  Portal and want to use the scheduling feature to publish content from a start date and remove it when it hits an end date then you will need to complete the following.

  1. In the Pages document library settings click on Versioning settings, then check the Require content approval for submitted items, and make sure the Create major and minor versions radio button is selected (needed to place content into draft state when expired).
  2. Click the Manage Item Scheduling link and check Enable scheduling of items in this list

A couple of things to be aware of:

  • When an item is removed as it has passed its scheduled end date then it places the item into draft mode.
  • Filtering (Web Parts, Views) on Scheduling Start Date and Scheduling End Date doesn’t seem to work
  • You may find adding your own Start Date and End Date provides filtering functionality in Web Parts and Views and you can also run a workflow against these columns for archiving.

Posted in MOSS 2007 | 6 Comments »

New U2U CAML builder

Posted by Clayton James on August 11, 2008

Kudos to Karine from U2U. She has come up with a new version for building CAML queries.

I have used the previous version of the U2U CAML Builder and have recommended it to others. This is the only way I chose to build CAML queries.

Download and let CAML become your friend ūüėČ

View the great new features and download here.

Posted in MOSS 2007, WSS 3.0 | Leave a Comment »

Site Columns Gallery Error

Posted by Clayton James on August 4, 2008

I was receiving this error the other day when trying to access the Site Column Gallery.

Object reference not set to an instance of an object.   at Microsoft.SharePoint.ApplicationPages.FieldListRenderer.Render(HtmlTextWriter output)
¬†¬† at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) ……..

It turns out that if you create a site column using the object model it capitalises SITES in the url.

The root problem was with the request Url we used to open a SPSite/SPWeb.  It turns out that the request Url you use to construct a SPSite is *case sensitive* to the URL the way it is specified in SharePoint when it comes to creating SPField objects programmatically.  I know that seems a little hard to believe but we ended up driving this bug through PSS and after getting our Content DB demonstrating the problem into MS hands they walked through their code and identified the problem in the code behind mngfield.aspx and a requirement that any fields created via WSS must have been done so through an SPSite/SPWeb with case that exactly matches the target site.

One additional thing we found through this two month adventure researching this bug, you can see the fields in a root site collection via mngfield.aspx *if* you view the Site Column gallery from a sub site of the site collection where mngfield.aspx is returning the Unknown Error/Null reference exception.

Here is how you can determine if the fields you created have the appropriate case-sensitive scope.

1. Create a sub-site under the site collection.

2. From that sub-site, select Site Actions -> Site Settings -> under Galleries -> Site columns

3. The mngfield.aspx page should display, and you will see all site columns from the parent site collection.

Note that the Source column on this page is a hyperlink to the site collection mngfied.aspx.¬† If you click this link you’ll be taken to the familiar Unknown Error.

4 Look for any site columns that your code added to the site collection.¬† Pay particular attention to the letter-case of the Source hyperlink Url.¬† If you’re hitting the same issue we found, you’ll note that the hyperlink Url case does not match the case of the actual site.

Basically there is a line of code in the code behind mngfield.aspx that does a check something along the lines of “field.Scope == web.ServerRelativeUrl”.¬† The ‘==’ op was a poor choice as it doesn’t handle mixed cases.

Once a Site Column has been created via WSS using a SPWeb instance that was constructed with mis-matched case that column is broken, it cannot be fixed.¬† You’ll have to delete it and recreate under a SPWeb that was constructed either a) with a request Url of appropriate case or b) the safer option is to construct SPWeb/SPSite instance using their GUID constructor since that forces a Url lookup which will always be accurate.

So to fix this you need to navigate to the fieldedit.aspx page in the layouts directory, pass in the field name and then can you can delete the problematic site column.
e.g.  http://moss/sites/companyxyz/_layouts/fldedit.aspx?field=tt

Posted in MOSS 2007, WSS 3.0 | 9 Comments »

CustomAction & UrlAction

Posted by Clayton James on July 30, 2008

Some more CustomAction elements I have come across include:
– Rights: You can set a Rights property so only people with these rights can view the Custom Action
      You can also remove existing CustomActions based on rights
– RegistrationType and RegistrationId: I have previously set these to lists, however you can even set them to file types. So only files with a .html extension will see this custom action in the ECB menu


Here is some great information from Jan Tielens Blog.

I am including the content as I always reference it.

MSDN documentation also.

<Elements xmlns=”http://schemas.microsoft.com/sharepoint/”>
        Title=”My Link”
        <UrlAction Url=”_layouts/mypage.aspx”/>

If you build some functionality in the mypage.aspx, in many scenarios this page will need to know from which list the link originated. This can be done by using URL tokens in the UrlAction element:

<UrlAction Url=”_layouts/mypage.aspx?listid={ListId}“/>

The {ListId} URL token will be automatically replaced with the ID of the list, in which the menu item is shown. In the mypage.aspx, you can retrieve the value of the listid parameter by making use of the QueryString. Once you’ve got the ID, the object model can be used to get a reference to the SPList instance of that list. According to the documentation on MSDN, the following URL tokens can be used:

  • ~site – Web site (SPWeb) relative link.
  • ~sitecollection – site collection (SPSite) relative link.
  • In addition, you can use the following tokens within a URL:
    • {ItemId} – Integer ID that represents the item within a list.
    • {ItemUrl} – URL of the item being acted upon. Only work for documents in libraries. [Not functional in Beta 2]
    • {ListId} – GUID that represents the list.
    • {SiteUrl} – URL of the Web site (SPWeb).
    • {RecurrenceId} – Recurrence index. This token is not supported for use in the context menus of list items.

    Unfortunately there is no token that will give you the URL of the page on which the feature’s link is being displayed. In many cases you want to have that URL to be able to redirect, after you’ve shown your custom functionality, to the originating page. SharePoint itself uses this technique a lot: in many URL’s you’ll find the Source parameter:


    The URL above points to the NewForm.aspx for the a Links list. Normally when the user fill’s out this form and clicks OK, this page redirects to the default view of the list. Because this link has the Source parameter, when the user clicks OK (or cancel), the page will redirect to the default.aspx instead. You can add the Source parameter to a lot of pages in SharePoint, giving you full control over the redirecting.

    So the issue is: we want to include the URL of the originating page in the UrlAction element of the feature’s CustomAction, but all we get are a bunch of ID’s and some URL’s that are not useful for this scenario. As usual peeking in the machine room of SharePoint itself can give you some good ideas to solve this issue. The SharePoint guys themselves sometimes use Javascript functions in the UrlAction, instead of ordinary hyperlinks. Thus with some clever use of Javascript, it’s quite easy to solve the problem:

    <UrlAction Url=”javascript:window.location= ‘{SiteUrl}/_layouts/mypage.aspx?List={ListId}&amp;Source=’ + window.location”/>

    The actual link is a Javascript function that will navigate to a specific URL. This URL is a concatenation of the URL of the page to display (including for example the ID of the list as a parameter in the QueryString), and the Source parameter which is dynamically set the current page’s URL. Et voila, the constructed link will point to your page, and the redirect will always point to the page you started from.

    Extra: this tric can also be used to overcome a bug in SharePoint that causes a URL token of a CustomAction to be replaced only once. So if you have used the ListID token two times in a UrlAction element, only one of the token’s will be replaced with the actual ID of the list. The user “FlatEric” (what’s in a name?) explains this in the Community Content of the How to: Add Actions to the User Interface article on MSDN.

    I found an ugly way to bypass this flaw:
    <UrlAction Url=”javascript:function process(){var site='{SiteUrl}’;var item={ItemId};window.location.href=site+’/Lists/MyList/NewForm.aspx?ID=’+item+’&amp;Source=’+site+’/Lists/myOtherList/DispForm.aspx?ID=’+item;};process();”/>

  • Posted in MOSS 2007, WSS 3.0 | 19 Comments »

    Not everything works using the SPSecurity.RunWithElevatedPrivileges

    Posted by Clayton James on May 15, 2008

    Web parts and application pages run under the context of the of the windows account.

    “When the code behind a Web Part or a custom application page executes in response to a user request, the code does not execute under the worker process identity of the hosting Web application. Instead, WSS uses impersonation to switch the Windows security context over to another Windows account. In fact, if you look inside the web.config file for a WSS Web application, you will see the following entry:”

        <identity impersonate="true" />

    So if you are creating a web part that performs some type of operation…say updating user profiles using the UserProfileManager class, then you will receive permission errors because the windows account doesn’t have the required permissions. Even if you try to run the code using SPSecurity.RunWithElevatedPrivileges you will receive these permission errors.
    Note: It usually works in development because you are logged in as an administrator.

    So you have a couple of options:

    1. You will need to use the User Profile web service as there are some issues with the Object Model and elevation when using the  .
    2. Complete ASP.Net 2.0 impersonation and use an account that has permissions

    Posted in MOSS 2007 | 1 Comment »

    System Content Type IDs

    Posted by Clayton James on March 13, 2008

    Content Type ID-numbers Рreference list

    Name Content Type ID Description
    Item 0x01 Create a new list item.
    Reusable HTML 0x01002CF74A4DAE39480396EEA7A4BA2BE5FB Reusable HTML
    Reusable Text 0x01004D5A79BAFA4A4576B79C56FF3D0D662D
    Page Output Cache 0x010087D89D279834C94E98E5E1B4A913C67E Page Output Cache is a system content type template created by the Publishing Resources feature to define cache profiles.
    Document 0x0101 Create a new document.
    System Page Layout 0x01010007FF3E057FA8AB4AA42FCB67B453FFC1 System Page Layout is a system content type template created by the Publishing Resources feature, and it cannot be modified. To add columns to page layouts in the page layouts gallery and master page gallery, update the Page Layout content type template.
    Page Layout 0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811 Page Layout is a system content type template created by the Publishing Resources feature. All page layouts will have the column templates from Page Layout added.
    System Master Page 0x0101000F1C8B9E0EB4BE489F09807B2C53288F System Master Page is a system content type template created by the Publishing Resources feature, and it cannot be modified. To add columns to master pages in the page layouts gallery and master page gallery, update the Master Page content type template.
    Publishing Master Page 0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD1 Master Page is a system content type template created by the Publishing Resources feature. All master pages will have the column templates from Master Page added.
    Office Data Connection File 0x010100629D00608F814DD6AC8A86903AEE72AA
    Universal Data Connection File 0x010100B4CBD48E029A4AD8B62CB0E41868F2B0 Provide a standard place for applications, such as Microsoft Office InfoPath, to store data connection information.
    System Page 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2 System Page is a system content type template created by the Publishing Resources feature, and it cannot be modified. To add columns to the Pages library, update the Page content type template.
    Page 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39 Page is a system content type template created by the Publishing Resources feature. The column templates from Page will be added to all Pages libraries created by the Publishing feature.
    Article Page 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D Article Page is a system content type template created by the Publishing Resources feature. It is the associated content type template for the default page layouts used to create article pages in sites that have the Publishing feature enabled.
    Welcome Page 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF390064DEA0F50FC8C147B0B6EA0636C4A7D4 Welcome Page is a system content type template created by the Publishing Resources feature. It is the associated content type template for the default page layout used to create welcome pages in sites that have the Publishing feature enabled.
    Redirect Page 0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900FD0E870BA06948879DBD5F9813CD8799 Redirect Page is a system content type template created by the Publishing Resources feature. It is the associated content type template for the redirect page layout
    Form 0x010101 Fill out this form.
    Picture 0x010102 Upload an image or a photograph.
    Unknown Document Type 0x010104 Allows users to upload documents of any content type to a library. Unknown documents will be treated as their original content type in client applications.
    Master Page 0x010105 Create a new master page.
    User Workflow Document 0x010107 Items for use in user defined workflows.
    Wiki Page 0x010108 Create a new wiki page.
    Basic Page 0x010109 Create a new basic page.
    Web Part Page 0x01010901 Create a new Web Part page.
    Link to a Document 0x01010A Create a link to a document in a different location.
    Dublin Core Columns 0x01010B The Dublin Core metadata element set.
    Event 0x0102 Create a new meeting, deadline or other event.
    Issue 0x0103 Track an issue or problem.
    Announcement 0x0104 Create a new news item, status or other short piece of information.
    Link 0x0105 Create a new link to a Web page or other resource.
    Contact 0x0106 Store information about a business or personal contact.
    Message 0x0107 Create a new message.
    Task 0x0108 Track a work item that you or your team needs to complete.
    Workflow Task 0x010801 A work item created by a workflow that you or your team needs to complete.
    Office SharePoint Server Workflow Task 0x01080100C9C9515DE4E24001905074F980F93160 A work item created by a workflow that you or your team needs to complete.
    Administrative Task 0x010802 An administrative work item that an administrator needs to complete.
    Workflow History 0x0109 The history of a workflow.
    Person 0x010A
    SharePointGroup 0x010B
    DomainGroup 0x010C
    Post 0x0110 Create a new blog post.
    Comment 0x0111 Create a new blog comment.
    Far East Contact 0x0116 Store information about a business or personal contact.
    Folder 0x0120 Create a new folder.
    RootOfList 0x012001
    Discussion 0x012002 Create a new discussion topic.

    Posted in MOSS 2007, Office 12 | 3 Comments »

    Moss case studies and Internet sites

    Posted by Clayton James on November 29, 2007

    More SharePoint 2007 case studies and Internet sites.


    Posted in Articles, MOSS 2007 | Leave a Comment »

    SharePoint 2007 Security: One stop shop

    Posted by Clayton James on November 21, 2007

    Joel has written a great entry on best practices and common pitfalls in SharePoint 2007 security. Also has many links to other resources.

    Great work again Joel. Bookmarked!


    Posted in MOSS 2007 | 1 Comment »

    Upgading customisations from SPS2003 to Moss 2007

    Posted by Clayton James on November 19, 2007

    2 must have whitepapers have recently been released on upgrading customisations from sps2003 to moss 2007.

    Issues when upgrading from sps2003 to moss 2007  occurs when parts of sps2003 has been customised. These papers provide an indepth guide to all areas that may have been customised and  

      These papers (Part 1 & 2) cover all areas of sps2003 customisations and provide recommended upgrade paths for each area. Very informative and well written.

    Part 1

    Part 2

    Posted in MOSS 2007 | Leave a Comment »

    Moss workflow presentation

    Posted by Clayton James on October 29, 2007

    I recently did a Moss/Workflow presentation with a good friend Mark Daunt .

    There wasn’t a need to blog about this before hand as it was sold out in a few days (I say sold out loosely due to it being a free event but you get the drift). It was great to see so much support for Moss and workflow in my home town in Brisbane, there were approximately 60-70 people each night. The event started out discussing workflows in general, workflow foundation, out-of-the-box workflows in Moss…with demo, SharePoint designer workflows…with demo, visual studio workflows…no time for demo and administering and reporting workflows inside Moss…with demo.

    All of this jammed packed into one hour. (and a bit) I enjoyed the event and thought the content we covered was spot on for a general audience.

    Posted in MOSS 2007, Rants | Leave a Comment »

    Log errors to SharePoint Log file

    Posted by Clayton James on October 29, 2007


    I came across this nice code snippet to log exceptions to the default SharePoint log file. (Putting it here for the memory bank).


    catch(Exception myException)



    Occurred: {0} || {1}”, myException.Message, myException.StackTrace);


    Posted in MOSS 2007 | 5 Comments »

    Moss Internet site articles

    Posted by Clayton James on September 16, 2007

    The SharePoint team have just released two much needed articles.

    Posted in MOSS 2007 | Leave a Comment »

    MOSS Accessibility Kit

    Posted by Clayton James on August 22, 2007

    I am currently in Perth teaching the Moss 2007 Bootcamp course. While I was here I was lucky enough to attend the Moss user group and see Sezai present on WCM. One of major topics that surfaces when discussing WCM and MOSS is the development process of creating a site that complies with W3C XHTML standards, WAI guidelines, Section 508 standards. This isn’t an OOB solution.

    I have come to the understanding that there are basically three options you can use:

    • ¬†

    • Write custom field controls to control the html output.



    • Use HiSoftwre Moss Accessibility Kit: endorsed by Microsoft.




      The Accessibility Kit for Office SharePoint Server will include site templates, Web parts, documentation, instruction and tutorials enabling partners and customers to develop Web sites that conform to the guidelines set out in Section 508 of the U.S. Rehabilitation Act and the W3C’s Web Content Accessibility Guidelines (WCAG). The solution will also provide accessibility updates for Office SharePoint Server templates and Web parts for Web publishing, corporate intranet, team and project collaboration sites and more. This allows users to create a site and replace “out-of-the-box” MOSS components with accessibility kit templates, reusable Web content and Web parts.


    For me the decision is simple.

    Posted in MOSS 2007 | 9 Comments »

    Fast Application Pool Recycler: and its free

    Posted by Clayton James on July 26, 2007

    I just came across a great tool for recycling IIS application pools or even performing an IIS Reset. Simply click the system tray utility and select the application pool you want to recycle.

    This tool is especially useful for WSS/MOSS developers who need to regularly recycle application pools when developing in the SharePoint environment.


    Quote from site
    “This freeware application is a System Tray utility for providing quick access to common¬†IIS tasks which are useful on a SharePoint development box. It may also be useful to others working with IIS. In essence, it enumerates the app pools on your box and lets you right click ’em to bounce ’em!

    For those who like the old fashioned way then you can wrap this up in a .bat file

    cscript c:\windows\system32\iisapp.vbs /a “%SharePointAppPool%” /r

    Where %SharePointAppPool% is the app pool you are wanting to cycle.

    Or you can use issapp from a command prompt to view the process id – thanks Doug

    Posted in MOSS 2007, WSS 3.0 | Leave a Comment »

    MOSS 2007 Resources

    Posted by Clayton James on July 17, 2007

    [This is a work in progress and content will be categorized into sections]

    Code Plex Projects


    Planning and Architecture

    Plan for availability


    Records Mgt



    Great resources on all things Document & Records management.


    Australian MOSS Case Studies


    Australian MOSS User Groups






    Forms Authentication
    Step-By-Step guide to setting up MOSS Forms Authentication


    Dual Authentication: Windows and Forms authentication


    Kerbros Setup


    Microsoft.com running MOSS


    Configure additional administrative settings


    HummingBird and SharePoint Integration



    Free e-Books


    Hosting InfoPath inside a webpart


    Installing MOSS 2007 on a VPC


    SharePoint Products and Technologies: Web Part Templates for Visual Studio .NET


    WSS templates ‚Äď Test the fab 40 templates to see which ones you like


    Hosting infopath in a WebPart – screen shots


    Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System

    Brief Description

    The Microsoft Best Practices Analyzer for Microsoft Windows SharePoint Services 3.0 and the 2007 Microsoft Office System creates detailed reports to help administrators achieve greater performance, scalability, and uptime.




    Reporting Services

    Publish a report to SharePoint library from SharePoint Designer

    Connect SQL Reporting Services to a SharePoint List


    Customize Moss Navigation

    Integrate Telerik Controls WSS / MOSS

    VS.Net Workflow – details correlation tokens, taskid, tasktoken, etc..

    Web Parts, CAS and Soluton Deployment

    People Picker search scopes

    Dispose WSS objects



    Common ListTemplate Ids: use in Cross list query, Features

    100 Generic List

    101 Document Library

    102 Survey

    103 Links List

    104 Announcements List

    105 Contacts List

    106 Events List

    107 Tasks List

    108 Discussion Board

    109 Picture Library

    1100 Issue Tracking


    SharePoint Blog

    List Exists

    Posted in MOSS 2007 | Leave a Comment »