Yesterday, I gave a session in the Israeli Office User Group about Silverlight & SharePoint integration. I have to say that the feedback was AMAZING. I'm attaching the Session's presentation: "Light Up The MOSS" so you can download and go over the links.
By the way: A full day about Silverlight & MOSS is planned for January. It'll be very comprehensive and much more low level than the User Group. It'll be on the Events section of Microsoft very soon but for now just SAVE THE DATE: 21/1/09.
P.S - I understood that some of you can't see the file so I also uploaded it into a free Rapidshare server. Here's the link
Just a little something that can help the poor guys that had to use Export/Import or Content Migration methods instead of the straight-forward and hassle-free Backup/Restore.
As you may have noticed, Content Migration features around WSS Sites some major limitations. The two large one you should remember are that Content Migration an only import data from sites that consist of the same language as the entire target site collection and are using the same site template.
That means that even if you have the English Language pack on you MOSS Installation and you created an English WSS Site to host the imported data, you still can't import anything if the entire Site Collection is not in English (Hebrew for example). Sounds awfully problematic but that's just the way it is and there is no supported way around it. The Cmp file (Content Migration Package) that stores the exported data contains definitions about the parent site collection's language so Language Pack are pretty useless at this point. You'd better off creating the structure of the site and migrate the lists one by one...
Another limitation is the Site Template of the targeted site. You can only import data to a web site of the same template. Well, that would actually sound fair if the stsadm (or any other tool that user Content Migration API) would have been kind enough to hint us about the requested template of the CMP package that we want to import. Instead, you get the Site Template Code that are used internally by Microsoft and try to figure out what is the need template. Well, you can imagine that codes like SRCHCEN#0 or OSRV#0 can be a handful to understand.
Well, at least in this matter – I can help. After wasting a bit of time around it, I managed to compile a full list of Templates and their codes. That means that next time you'll see an error code with yet another mysterious Template Code, you should have no problem deciphering it using this table.
GLOBAL#0 = Global template (1033)
STS#0 = Team Site (1033)
STS#1 = Blank Site (1033)
STS#2 = Document Workspace (1033)
MPS#0 = Basic Meeting Workspace (1033)
MPS#1 = Blank Meeting Workspace (1033)
MPS#2 = Decision Meeting Workspace (1033)
MPS#3 = Social Meeting Workspace (1033)
MPS#4 = Multipage Meeting Workspace (1033)
CENTRALADMIN#0 = Central Admin Site (1033)
WIKI#0 = Wiki Site (1033)
BLOG#0 = Blog (1033)
BDR#0 = Document Center (1033)
OFFILE#0 = Records Center (1033)
OFFILE#1 = Records Center (1033)
OSRV#0 = Shared Services Administration Site (1033)
SPS#0 = SharePoint Portal Server Site (1033)
SPSPERS#0 = SharePoint Portal Server Personal Space (1033)
SPSMSITE#0 = Personalization Site (1033)
SPSTOC#0 = Contents area Template (1033)
SPSTOPIC#0 = Topic area template (1033)
SPSNEWS#0 = News Site (1033)
CMSPUBLISHING#0 = Publishing Site (1033)
BLANKINTERNET#0 = Publishing Site (1033)
BLANKINTERNET#1 = Press Releases Site (1033)
BLANKINTERNET#2 = Publishing Site with Workflow (1033)
SPSNHOME#0 = News Site (1033)
SPSSITES#0 = Site Directory (1033)
SPSCOMMU#0 = Community area template (1033)
SPSREPORTCENTER#0 = Report Center (1033)
SPSPORTAL#0 = Collaboration Portal (1033)
SRCHCEN#0 = Search Center with Tabs (1033)
PROFILES#0 = Profiles (1033)
BLANKINTERNETCONTAINER#0 = Publishing Portal (1033)
SPSMSITEHOST#0 = My Site Host (1033)
SRCHCENTERLITE#0 = Search Center (1033)
SRCHCENTERLITE#1 = Search Center (1033)
SPSBWEB#0 = SharePoint Portal Server BucketWeb Template (1033)
Hope this helps…