Catch my Point

MSDN has a good list of "Visual How To" Source: http://msdn2.microsoft.com/en-us/library/bb418736.aspx Activating Auditing Programmatically for a Single Document Library in Windows SharePoint Services 3.0 Activating Auditing Programmatically for a Site Collection in Windows SharePoint Services 3.0 Configuring IntelliSense with CAML files when developing for SharePoint 2007 Create a Custom HttpHandler in Windows SharePoint Services 3.0 Creating a Feature for an Entry Control Block Item in Windows SharePoint Services 3.0 Creating a Feature for the Site Actions Menu in Windows SharePoint Services 3.0 Creating a Solution Package in Windows SharePoint Services 3.0 Creating a Visual Studio Project for Windows SharePoint Services 3.0 Creating an Application Page in Windows SharePoint Services 3.0 Displaying Data by Using the SPGridView Control in Windows SharePoint Services 3.0 Reading Entries from the Audit Log in Windows SharePoint Services 3.0 Reading ListId and ItemId from an Application Page in Windows SharePoint Services 3.0 Running Commands with Elevated Privileges in Windows SharePoint Services 3.0 Writing Custom Entries to the Audit Log in Windows SharePoint Services 3.0

During the SharePoint Server solution development process, establish an authoring environment where the following is possible:

• Content developers can use SharePoint Designer to create and modify content (master pages, custom pages, style sheets, and so on) within a mirrored site collection that actually represents the production environment.
• Authoring activities make use of SharePoint source control and publication features.
• Content developers have the ability to modify the existing production environment and conduct publication using a content management path to the production Web farm.
• A production-class environment is provided by the authoring environment, such that all assemblies, Web Parts, SharePoint Server solutions, and structural changes that are deployed to the production Web farm are also deployed to the authoring environment.
• The authoring environment can exist within the production environment as the SharePoint Server Web content publication feature provides a level of abstraction between proposed changes to content and approved changes.
• From a team perspective, the shared authoring environment is more effective than individually separate authoring environments.
• SharePoint Designer artifacts do not need to be integrated with enterprise source control.
• Enterprise source control (such as Team Foundation Server) should be used strictly for assembly development in a team environment, while the effort to integrate content management items into source control is not a supported process.
• Attempts to integrate items into enterprise source control that are considered SharePoint Designer content items and part of content development require extensive workarounds involving manual processes and procedures.
• Items built into SharePoint Designer as content are subject to the Web publication process of source control, approval, and publication.

Use content management paths to publish SharePoint Designer changes to production environments. Source http://msdn2.microsoft.com/en-us/library/bb428899.aspx

http://mindsharpblogs.com/wayne/archive/2005/06/15/497.aspx has great information on using custom source (AD Query) to import users in Active Directory Groups into SharePoint Profile database.(&(objectCategory=Person)(objectClass=User) | (memberOf=CN=Corporate East,OU=Administrative,OU=Distribution Lists,OU=East,DC=domain,DC=local)(memberOf=CN=Corporate West,OU=Administrative,OU=Distribution Lists,OU=West,DC=domain,DC=local)(memberOf=CN=Corporate EMEA,OU=Administrative,OU=Distribution Lists,OU=EMEA,DC=domain,DC=local))Only Users in the AD Distribution List group will beimported and not any users from nested groups (if you another group as its member)

Cornelius J. van Dyk has a gerat blog entry about Capacity planning and also provided a tool to calculate Number of Web Front end Servers needed. In a nutshell, below diagram explains number of servers needed based on transactions per second.