Last week I got an opportunity to work with SharePoint Search. As you could imagine it didn’t go that easy at all and to be honest the SQL-like statements didn’t make it for me at all. And unless I’ve seriously missed something, I’ve found out that there is no easy way to exclude empty text results in SharePoint Search. At least it seemed so…
Microsoft Office SharePoint Server (MOSS) 2007 provides architecture for designing and developing scalable solutions. Two of these concepts are Site Collections for separating information and Variations for delivering multilingual solution. While working with both concepts – especially in Web Content Management (WCM) solutions I have found out that there is no easy way to create Site Collection or Variation relative links.
Setting the correct value for the FeatureId attribute of the ListInstance element is just one of things you can easily overlook on a sunny Friday afternoon when your mind is already enjoying the weekend. It’s like forgetting to read the small letters underneath a contract you’re about to sign: it seems like it all is going to be okay but at the end of the day you’ll be in troubles.
Some time ago I wrote about provisioning instances of Content Query Web Part (CQWP) in a structured and repeatable way. Just recently I have found out that there is one very important thing you have to be aware of, if you don't want to break the deployment process.
When using SharePoint search in a Web Content Management (WCM) solution you are very likely to create your scope which will include Publishing Pages only. As other pages like Application Pages and Lists' Forms are not accessible by anonymous visitors you don't want them to appear in the search results on the public site. While creating what I call a 'public scope' is rather straight-forward there is one thing you have to keep in mind to make it work as expected.