Comments on: Theme-amajig: Updating SPTHEMES.XML Through a Feature

By: George

George — Tue, 23 Feb 2010 20:32:18 +0000

Nice work – does exactly what I need to do. Thanks for the example!

By: Deployment of Resource files (*.resx) to App_GlobalResources under SharePoint - Shawn Cicoria - CedarLogic

Sun, 31 Jan 2010 18:45:05 +0000

[...] http://solutionizing.net/2008/07/09/updating-spthemesxml-through-a-feature/ [...]

By: Deployment of Theme and Resource files via Feature / Timer Jobs - Shawn Cicoria - CedarLogic

Sun, 31 Jan 2010 18:32:36 +0000

[...] http://solutionizing.net/2008/07/09/updating-spthemesxml-through-a-feature/ [...]

By: Andy Burns

Andy Burns — Fri, 26 Jun 2009 14:05:17 +0000

Vitaly – there is another option for that than just themes – the AlternateCssUrl. This has a couple of benefits:
1) It applies to the DatePicker’s pop-up calendar (which, curiously, doesn’t obey themes)
2) Applying a them copies it to your site. There is only 1 copy of the files for the alternate CSS approach.

Although only the Publishing sites have a user interface for setting the AlternateCssUrl, all sites (SPWebs) have this property, and you can set it in a feature receiver…

http://www.novolocus.com/2008/11/10/where-to-put-css-when-branding/
http://www.novolocus.com/2008/10/20/style-the-datepicker-using-an-alternate-css/

By: Vitaly Mogoreanu

Vitaly Mogoreanu — Wed, 10 Jun 2009 15:09:34 +0000

I am not a fan of themes either. However I do not know another way to style site management or user management pages (_layouts/people.aspx). Another possible use of this approach is to copy .browser files to AppBrowser folders of your application on different front ends. Basically anything else MS left behind
Thanks for the article!

By: Keith Dahlby

Keith Dahlby — Wed, 10 Jun 2009 14:06:01 +0000

Thanks for the comment! Indeed I haven’t actually run it on a farm (I rarely use themes), however I modeled the job definition on SPWebConfigJobDefinition which seems to work fine. I’m glad you were able to get it to work – has anyone else seen this issue?

By: Vitaly Mogoreanu

Vitaly Mogoreanu — Tue, 09 Jun 2009 16:18:51 +0000

Nice idea. Have you actually run it on a farm? I had to change the code to iterate through the servers, not services as following:

foreach (SPServer server in farm.Servers)
{
    switch (server.Role)
    {
        case SPServerRole.Application:
        case SPServerRole.SingleServer:
        case SPServerRole.WebFrontEnd:
            //Submit Job
            break;
        default:
            break;
    }
}

By: Automatically Updating the SPTheme.xml File « Devology Solutions Blog

Automatically Updating the SPTheme.xml File « Devology Solutions Blog — Sat, 23 May 2009 01:02:51 +0000

[...] I found this originally on Keith Dahlby’s blog at: Theme-amajig: Updating SPTHEMES.XML Through a Feature [...]

By: Keith Dahlby

Keith Dahlby — Fri, 28 Nov 2008 16:49:20 +0000

David, Pieter ~ Thanks for pointing out the error - it seems those code segments were copied from different iterations of the final product. Over time the variable changed from existingThemeNode to themeNode to just node - the post should be consistent now. I've also uploaded a working sample solution to CodePlex here. Cheers ~ Keith

By: Pieter

Pieter — Fri, 28 Nov 2008 10:16:49 +0000

well it looks like a nice post, but I’m wondering if it even will succesfully build…

I haven’t tried the code yet, but one of the first things I saw was the following:

if (themeNode != null)
existingThemeNode.ParentNode.RemoveChild(themeNode);
}

but over the whole bunch of code there is no declaration for “existingthemenode”, so how in the “sharepoint” world will this code ever work? and I agree with the previous poster about the “node.Parentnode….” ….. it simply doesn’t exist…

Regards,