MOSS Themes - Order of loading

There are already some blog posts on the order with wich SharePoint loads its css files. So I won't go into detail on that.

However I want to give you some info on an issue I had not long ago.

Situation

Custom Masterpage
Custom Theme on Root site
Other Custom Theme on child that touches some similar styles with other colors

Problem

The last css to get loaded was the one of the parent theme

Solution

Moving this tag

<SharePoint:Theme ID="Theme1" runat="server"/>

to be in front of

<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server">
</asp:ContentPlaceHolder>

More Info

I used a custom masterpage together with a theme. Because I wanted to do all css with the theme I moved the tag to just in front of the tag.
However when you configure a theme on a subsite it gets placed in the "additional page head" wich caused the above mentioned caution.

Moral

When designing your custom masterpage, think twice when moving tags .. and test test test.

Kind regards
Steven

Going for MCPD Web Developer

After completing the MOSS Configuration examn, i told you all that I didn't know wich would be next. Well .. no I'm here to tell you that Examn: 70-547 (PRO: Designing and Developing Web-Based Applications by Using the Microsoft .NET Framework) is next on my list :)

If anyone has usefull tips about this examn, your welcome to post them here.

I'm planning on using the following book as the basis for my studies. Does it contain enough information combined with the test exam that comes with the book? Or is it required to consult some extra resources?

MCPD Self-Paced Training Kit [Exam 70-547]: Designing and Developing Web-Based Applications Using the Microsoft .NET Framework

Extracting assemblies from the Global Assembly Cache: The Options

This is mostly ment as a reminder for myself because I keep forgetting it :)

There are several options:
- Command line copy
- Unregistering shfusion.dll
- Bypassing shfusion without unregistering

The last one is definetly my favorite, Just open the run command box (or quick search box in Vista) and enter the following:
%windir%\assembly\gac
This will open an explorer window while bypassing de shfusion.dll file that limits functionality