Handling AccessDenied Exception to implement our logic

The SPUtility.HandleAccessDenied method provides the functionality to redirect users to the standard "Access Denied Page" pragmatically, thus asking them to re-logon. One of the scenarios of such usage is the public sites, where access to the standard SharePoint specific pages still exists and you want to block those pages

However, you can handle access denied exception via SPSecurity.CatchAccessDeniedException = true

Access deined exception is handled by sharepoint platform and user will be redirected to _layouts/AccessDenied.aspx page if user doesnt have permission to perform that task. This might casue usability problem in some cases. You can handle access denied exception in your code by setting CatchAccessDeniedException value to true.
Following code snippet shows how to handle access denied exception:

bool catchException = SPSecurity.CatchAccessDeniedException;
SPSecurity.CatchAccessDeniedException = false;
try
{
//updating list item
SPList list = SPcontext.Current.Web.List["TestList"];
SPListItem item = list.Items[0];
item["title"] = "Some value";
//If user doesnt have permission, exception will be thrown
//If value of CatchAccessDeniedException is true, then user will be
//redirected to AccessDenied.aspx page
item.Update();
}
cach(Exception ex)
{
//Your custom error message can be shown here
}
finally
{
//reset the flag to original value
SPSecurity.CatchAccessDeniedException = catchException;
}

Content Deployment - Best Practices

 Full content deployment is done only on empty site collection, if we want to deploy the content only for the modifiled pages, content  then we go with incremental deployment.

Content deployment copies content from a source Microsoft Office SharePoint Server 2007 site collection to a destination site collection. The entire source site collection can be copied (full), or a subset of sites can be copied (incremental). In either case, content deployment is incremental by default, deploying only changed pages and related assets (such as images). You can also do a full deployment of all content; however, you should only run a full deployment job on an empty site collection. Also, a Quick Deploy feature supports deployment of a single page by authors

http://blogs.technet.com/b/stefan_gossner/archive/2009/01/16/content-deployment-best-practices.aspx

SSL configuration in Sharepoint with Win2008 and IIS7

http://bable.cybermarshall.com/2009/01/06/adding-ssl-support-to-an-existing-wss-30-sharepoint-2007-site/

http://www.sharepointassist.com/2009/02/01/sharepoint-and-ssl-configuring-https-for-sharepoint-on-windows-server-2008-iis7/

http://www.tonytestasworld.com/post/2009/06/26/Configure-SSL-with-SharePoint-Web-Applications-and-how-to-force-SSL-redirect.aspx

Sharepoint 2010 Videos

http://www.bing.com/videos/browse/more?q=browse:more/Related%20Videos&query=%3CvideoQuery%3E%3CvideoFilter%3E%3Ctype%3ERelated%3C/type%3E%3Csource%3EMsn%3C/source%3E%3CsafetyFilter%3EStrict%3C/safetyFilter%3E%3CrelatedAlgorithm%3E1%3C/relatedAlgorithm%3E%3Cuuids%3E%3Cuuid%3Eadc12310-ad50-4ffa-9cc5-c104596849ee%3C/uuid%3E%3C/uuids%3E%3C/videoFilter%3E%3CvideoSort%3E%3CsortField%3EDate%3C/sortField%3E%3CsortDirection%3EDescending%3C/sortDirection%3E%3C/videoSort%3E%3C/videoQuery%3E&title=Related%20Videos



http://www.bing.com/videos/watch/video/getting-started-sharepoint-2010-built-in-sharepoint-controls/10tkfuxp9

http://www.sharepoint-tips.com/search/label/SharePoint%202007

Getting user profile values that support multiple value

if (Profile[this.UserProfilePropertyName].Count == 1)
    return Profile[this.UserProfilePropertyName].Value.ToString();
else
{
    StringBuilder ret = new StringBuilder("");
    UserProfileValueCollection values = Profile[this.UserProfilePropertyName];
    System.Collections.IEnumerator allValues = values.GetEnumerator();
    while(allValues.MoveNext())
    {
        ret.Append(allValues.Current.ToString());
        ret.Append(";");
    }
    return ret.ToString();
}