CSS best practice

Inline style is not a good practice if you want to work with styles, as it is difficult to update if you want to make a modification across the site.

So, some WEB-UI developers start making a new framework to use while making their styles without using the inline style, they develop a class for each style, ex: .Width150px { width:150px;} and another one .Red {color:red;} and use it like this class=”Red Width150px”!
For me, using inline style is better as it will be much more faster while developing than using the above way.

The better practice for using CSS is by defining a meaning full name that describes the thing that will take the style, ex: .PageTitle {color:red; width:150px;} and give the DIV class=”PageTitle”, so I can update all the pages titles just by updating the CSS file, not going to each page title and update the class name.

DIVs vs TABLES

Lots of WEB-UI developers are thinking of replacing all the tables with DIVs which in my opinion is not right, they are using DIVs even if they want to render a table saying that it is better in performance.

But the right thing is: use div when you need it and use tables when you need it.
Using DIVs with CSS can make a lot of things that can’t be done by TABLEs, for example it you want to display data in rows and each row or some rows will not be aligned with the others and using TABLEs will make complicated TDs with a lot of COLSPANs, but displaying a form data can be done with TABLEs perfectly.

But it is preferred to use DIVs if you want to work with the page layouts, as you will be able to change the layout just by using the CSS.

setAttribute('maxlength', 5);

Setting maxlength with Javascript using the setAttribute() function will not work with IE like this: setAttribute('maxlength', 5);

You have to make it setAttribute('maxLength', 5);

Team Foundation Sidekicks

Team Foundation Sidekicks is a suite of tools for Microsoft Team Foundation Server administrators and advanced users providing Graphic User Interface for administrative and advanced version control tasks in multi-user TFS environments.
Version 2.2 of Team Foundation Sidekicks includes Permission Sidekick, Code Review Sidekick, Shelveset Sidekick, Labels Sidekick, History Sidekick, Workspace Sidekick and Status Sidekick in uniform GUI stand-alone application, and Visual Studio Integraton Package providing VS integration for all sidekicks as well as additional features such as Search Items dialog, dynamic History and Build Type editing support.
Single installation package contains versions of application compatible both with Team Foundation Server 2005 and Team Foundation Server 2008.

Move site collections to a new database (split a content database) (Windows SharePoint Services 3.0)

This is a very usefull article talking about how to move a site collections to a new database

You can also have a look on Microsoft SharePoint Administration Toolkit