I had been customising Sharepoing theme lately in 2010 version, and i have to say it's not very fun, mainly due to lack of documentation online and a big change in UI elements comparing to version 2007.
Often times we have to customise SharePoint’s stock user interface, particularly elements such as edit block, toolbar, menus, etc. It’s possible to have our own custom items in these areas, but first it would be a lot easier to understand their names and locations respectively.
I have been playing around with LINQ in Sharepoint object model and I have to say I’m quite impressed. It does shorten the amount of code we write and works just as great or better.
A handy way to select distinct records from SPListItemCollection set queried from CAML query.
Sharepoint has a feature that allows us to migrate list data structure and content to a different site so that we do not have to re-create them. This is done through list settings -> save list as template. List template is a powerful function which can save the data structure of a list as well as its content.
Lately we found a very interesting fact of Sharepoint, which I think is worth writing a post about. Although it is very rare that someone will read directly into Sharepoint database to retrieve information, but for some hardcore users, especially with my last post regarding how Sharepoint stores data in backend database, one can easily read into Sharepoint Prod_Content database and do CRUD transactions.
I spent quite some time today fixing this problem of accessing a list item in parent web. What I had to do was to access a list item in a parent web, but it kept crashing as if there's no permission given to access it.
Time and time again, I use these methods in coding for Sharepoint. These include methods for querying a list, bind a Dropdown List to a list, and bind a Dropdown List to a multiple choice field.