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.
Windows SharePoint Services (WSS) v3 introduces the concept of Site Columns: reusable fields which can be used for creating content definition across the whole Site Collection. While this concept allows you to manage the way content is stored, you have to be really careful when working with Site Columns in custom development.
Windows SharePoint Services v3 ships with a possibility to create RSS Feeds for every List. This feature is quite powerful as it allows you to create multiple RSS Feeds for one List based on Views. If you have worked with Lists at least a bit, you know that you can quite easily create a custom View using the standard SharePoint interface. Without any problems you will be able to define the filter and apply the sorting criteria.
Recently I've been working on a piece of code which would obtain an instance of SPFile using either a GUID or the server relative URL. You don't have to search long to find out that the SPWeb provides a method to do that: GetFile(String). According to the WSS v3 SDK it should return the file object located at the specific URL.
The Content Editor Web Part (CEWP) shipped with SharePoint 2007 is just one of these ordinary Web Parts: they don't introduce any extraordinary functionality, yet we all use them in our solutions for some reason. Because this Web Part is all about displaying the Rich Text you have entered, you might think, that it is almost impossible to mess that up. Unfortunately...