Version 1.7.0 Release

Rating: No reviews yet
Downloads: 7313
Released: Jun 17, 2008
Updated: Apr 19, 2009 by dougleung
Dev status: Stable Help Icon

Recommended Download

Application SharePoint Branding Tool v1.7.0
application, 56K, uploaded Jun 16, 2008 - 7313 downloads

Release Notes

This tool can be used apply the following actions for multiple Site Collections, and Child Sites:
-modify Themes,
-modify MasterUrl (Master Page),
-modify CustomMasterUrl (System Master Page),
-modify SiteLogoUrl (Site Logo),
-modify SiteLogoDescription (Site Logo Alternative Text),
-modify AlternateCssUrl (Custom CSS Style Sheet)
-view various properties of sites and themes at a glance

Selection of sites can be filtered by the Site Template used.

How to start the tool?
1. Extract all files in this package to a folder on a Windows server with WSSv3 or MOSS2007 installed
2. Ensure the user logged in/running the tool has priviledges to modify sites
3. Make sure you backup your sites before applying changes
4. Double click on SharePointBrandingTool.exe to run

Release Notes
Version 1.7.0
Douglas Leung
12:38 AM 17/06/2008
Updated 6:08PM 19/04/2009

Enhancements to include:
-UI Improvement: Less intrusive messages
-UI Improvements: Status Strip for operation reporting, etc
-Different SharePoint language version support (Dynamic install path support - for Spanish support)
-Improved error message reporting
-Improved operation reporting

Tips: Right click around to discover some new functionality!

-Have not implemented RunWithElevatedPriviledges because user should only be able to modify sites, if they have the access and privileges to.
-Have not implemented Remote Operation yet (lets hope time will allow in the future)
-This version is known to only work on SharePoint environments with locale "English - United States" (LCID: 1033).


To support various language versions of SharePoint, the code now loads values from "C:\Documents and Settings\{current user}\Local Settings\Application Data\Douglas\SharePointBrandingTool.vs_Url_yad5xgfsubxbu24baoicwfzfolv1wc5j\\user.settings".
Update the UserLanguage value with the respective locale lcid on your server. For example,

<setting name="UserLanguage" serializeAs="String">

Update the SharePointInstallPath to support different paths to the 12 hive
<setting name="SharePointInstallPath" serializeAs="String">
<value>C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\</value>

The code loads a list of LCID definitions to an internal class. The lanuage names and lcid's are used to load values into
the Options UI. These names however, will only appear if the respective directory is found on the server.

The following is an example of the structure:
<?xml version="1.0" encoding="utf-8" ?>
<localization xmlns:xsi="" xmlns:xsd="">
<language>Spanish - Spain (Modern Sort)</language>
<language>Spanish - Spain (Traditional Sort)</language>

You can append addition nodes to support additional languages. For more information go to

Reviews for this release

No reviews yet for this release.