Disclaimer: All information in this article is provided “AS IS” with no warranties, and confers no rights and on a “use at your own risk” basis.

The RunWithElevatedPrivileges method is used to for this purpose.

VB.Net Example:

Sub GetSiteInfo()

Dim siteColl As SPSite = SPContext.Current.Site

Dim site As SPWeb = SPContext.Current.Web

Using ElevatedsiteColl As SPSite = New SPSite(siteColl.ID)

Using ElevatedSite As SPWeb = ElevatedsiteColl.OpenWeb(site.ID)

End Using

End Using

End Sub

After you write a method such as GetSiteInfo you can execute it with elevated privileges by invoking the RunWithElevatedPrivileges method and passing a delegate reference created with the Visual Basic AddressOf operator. (note the creation of new SPSite and SPWeb objects)

SPSecurity.RunWithElevatedPrivileges(AddressOf GetSiteInfo)

Note:

You cannot use the objects available through the Microsoft.SharePoint.SPContext.Current property, because those objects were created in the security context of the current user. You need to create an new instance of the SPSite class and the SPWeb class after you elevate the privileges of your code by calling RunWithElevatedPrivileges within the context of a Windows SharePoint Services request. 

You can find more details at:

http://msdn.microsoft.com/en-us/library/bb466220.aspx

In SharePoint, log files are located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOG

To log errors/messages/exceptions to the default SharePoint log file use the following lines of code.

Microsoft.Office.Server.Diagnostics.PortalLog.LogString(”Exception Occurred: {0} || {1}”, Exc.Message, Exc.StackTrace);

Example Code snippet:

Try

{

}

catch (Exception Exc)

{

Microsoft.Office.Server.Diagnostics.PortalLog.LogString(”Exception Occurred: {0} || {1}”, Exc.Message, Exc.StackTrace);

}

The following table lists the recommended guidelines for site objects.

You can find more details at:
Plan for software boundaries (Office SharePoint Server)

If you are new to Sharepoint 2007, take a look at the following screencasts series.

• Building ASP.NET Web Parts for Windows SharePoint Services 3.0
• Creating a Custom Page Layout with SharePoint Server 2007
• Creating and Testing Features with Windows SharePoint Services 3.0
• Creating and Using Content Types in Windows SharePoint Services 3.0
• Creating and Using Event Handlers in Windows SharePoint Services 3.0
• Creating and Using Site Columns in Windows SharePoint Services 3.0
• Creating Custom Document Information Panels
• Creating Custom Task Panes in Visual Studio Tools for Office “v3″ June CTP
• Creating Custom Workflows with the SharePoint Designer 2007
• Creating Windows SharePoint Services Sites with Support for Wikis and Blogs
• Customizing a Windows SharePoint Services 3.0 site with the SharePoint Designer 2007
• Getting Up and Running with Excel Services
• Creating a Custom Page Layout with SharePoint Server 2007
• Creating Windows SharePoint Services Sites with Support for Wikis and Blogs
• Demo: Configure a SharePoint Server 2007 site to receive e-mail
• Demo: Deploy an administrator-approved form template
• Demo: Add a library to a Records Center site
• Demo: Enable Excel Services and data connections for a SharePoint team site

Consider the following while accessing the list  through Object model

1. SPWeb.GetList(string url)
   In this case, first it gets the list GUID from the url(database hit), then it loads the Meta data for that specific list.
2. SPWeb.Lists[“name”]
   This method loads the meta-data information of the all lists for the SPWeb object under consideration. and then it does SPList.Title comparison with metadata of all the lists returned and returns the first matching list from the SPWeb.Lists collection.

The first approach provides better performance than the second one.

If we pass GUID of the list  instead of a list name in the second approach it works similar to the first approach (SPWeb.GetList (url)), however passing a List Index would work similar to the second approach.

These  sites are really amazing and were built on SharePoint.

http://www.ferrari.com/
http://www.swissarmy.com/
http://www.eastman.com/
http://www.choosechicago.com/
http://www.kroger.com/
http://www.westernaustralia.com/
https://www.flybuys.co.nz/
http://www.energizer.com/

a. Go to SharePoint Central Administration Page
b. Select Operations and select Diagnostics logging under Logging and Reporting
c. In diagnostic logging page, select the Verbose mode and click on ok

Note:
1) It is not advisable to turn the verbose mode logging on. Turn it off once the required log is collected.
2) Sometimes Windows SharePoint Services Tracing service will stop when we do these modifications, you may need to restart the service.

• Groove (the offline/online synchronization tool Microsoft bought when it acquired Groove Networks) is being renamed and repositioned with the upcoming release as “SharePoint Workspace Manager.” Update on May 13: Microsoft has confirmed officially the renaming and is saying that SharePoint Workspace Manager and OneNote will be part of the Office 2010 ProPlus SKU. (Microsoft is declining to provide any other information, at this point, on its planned Office 2010 line-up.)

• SharePoint Server 2010 will be 64-bit only and require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2 to run. It also will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.

• SharePoint Server 2010 won’t support Internet Explorer 6. From the SharePoint Team blog: SharePoint 2010 will be “targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems. In addition we’re planning on an increased level of compatibility with Firefox 3.x and Safari 3.x on non-Windows Operating Systems,” according to the SharePoint Team Blog.

• SharePoint 2010 will feature a “Web-enabled Ribbon control” and support greater use of Silverlight controls

• CMIS support will allow interoperability between SharePoint 2010 and other content management systems

• The architecture supposedly won’t change as it did between SharePoint Server 2003 to Microsoft Office SharePoint Server 2007, thus insuring less compatibility issues and a smoother upgrade path (at least in theory)
• There’s a new feature, known as “faceted search” coming in the 2010 SharePoint release. No details available yet.

• A new version of FAST Search for SharePoint will be made available at a lower cost. Meanwhile, according to contractor and SharePoint blogger Lars Fastrup (whose blog entry is the source of a lot of this post), “the SharePoint team have scrapped their efforts to make the SharePoint search engine scale beyond 50 million documents in a single index. The argument will be to move to the FAST search engine instead.”

Source: www.zdnet.com