IncludeFolders=”??-??”

3 07 2008

For anyone whos gone to the msdn library (http://msdn.microsoft.com/en-us/library/ms460356.aspx) to find out what the IncludeFolders attribute on <Module> is for and been confronted with the description

“Optional Text.” (not helpful)

Here’s what I’ve managed to uncover. If you have a file (a.txt) and you’ve popped it in a folder (en-gb) in your feature folder you can reference it like this:

<Module Name=”TestFileDeploy” Url=”Style Library” IncludeFolders=”en-gb”>

<File Url=”a.txt” Name=”a.txt” Type=”GhostableInLibrary” />

</Module>

Now some of you may have spotted where this is going as “en-gb” and “??-??” have a similar format. :)

If you multiple language formats for the file, and hence have multiple language folders in your feature, all you need to do to deploy all your files is change the IncludeFolders to “??-??” and it will bring them across. You don’t need to add loads of <File> tags as its covered by IncludeFolders=”??-??”. Fantastic!





MySite, MyHome, MyProfile…

3 07 2008

MOSS MySites are an odd bread of site collection. And when it comes to customising them with new masterpages and themes, the branding never seems to be applied to MyProfile pages. This is because the MyProfile pages is lerking an a separate site collection outside of My Sites. I discovered this after reading Mark Arend’s posts ‘MySite Pages and Architecture’:

http://blogs.msdn.com/markarend/archive/2008/02/22/mysite-pages-and-architecture.aspx

You’ll discover that MySites incorporate pages from a separate PROFILES site collection. Also, applying styling to a profiles pages is applied across everyone’s MyProfile page as there is only ONE profiles site, unlike the separate MySites.





MSO_ContentDiv

2 07 2008

For anyone who has started to whittle back the OOTB master pages in MOSS 2007, and wondered why their webpart pages break – the tools panel appears below the main content – then check you still have the

<PlaceHolder id=”MSO_ContentDiv” runat=”server”>

</PlaceHolder>

This bespoke tag applies a </table> with no opening <table> when you click to ‘Edit’ any webpart. Without this little baby, your webpart pages will not render as expected.

See http://blogs.msdn.com/ecm/archive/2006/09/21/764759.aspx for a quick mention on issue.