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)

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.

Here are the steps:

1)Navigate to Site Actions à Manage Content And Structure

2)Go to Master Page Gallery in the folder list

3)Select “Show Related Resources” in the Tool Pane

4)Select the Page Layout for which you want to list all the resources

5)A list of all the related resources for the selected page layout will be listed in the bottom window.

Using .NET Reflector, you can browse the classes and methods of an assembly, you can examine the Microsoft intermediate language (MSIL) generated by these classes and methods, and you can decompile the classes and methods and see the equivalent in C# or Visual Basic .NET.

Dot Net Reflector Can be used for the following in SharePoint Scenario, :

• Understand on how SharePoint is doing something, to find what elements can be customized.
• Understand what members to override in classes you create that inherit from SharePoint classes
• .NET Reflector is also an excellent way to know the best practices. Because you get to see how the team at Microsoft actually implemented functionalities. And also you have lots of examples at your fingers tips.

Example Usage of Dot Net Reflector to Under Stand SharePoint Source Code:

· If you want to know on what is happening on load of OOTB Search Results Page then open Microsoft.SharePoint.ApplicationPages.dll and navigate to SearchResultsPage class and click on OnLoad method.

SharePoint DLLS:

• You can find all the SharePoint dlls under  C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI

• Some SharePoint assemblies(Microsoft.SharePoint.ApplicationPages.dll)  are stored in the _app_bin directory of the web application instead of the ISAPI directory in the 12-hive.

Obfuscation:

Sometimes, not too often, when Reflector is disassembling source code for you, it will show “This item is obfuscated and can not be translated” instead of code. This is done for some of the more “sensitive” areas of the code

Downloads:

.Net Reflector: http://www.red-gate.com/products/reflector/

Add-ins: http://www.codeplex.com/reflectoraddins

Note: Review the end user license agreement (EULA) for the relevant Microsoft products before using this tool.

]]> http://www.mossgeek.com/2009/02/understand-sharepoint-using-dot-net-reflector/feed/ 1 http://www.mossgeek.com/2009/02/how-to-manage-site-content-and-structure/ http://www.mossgeek.com/2009/02/how-to-manage-site-content-and-structure/#comments Wed, 18 Feb 2009 17:42:48 +0000 Geek http://www.mossgeek.com/?p=52 In a Sharepoint the Site Content and Structure page is cool tool for site administrators to manage site content and structure. You can do lot of stuff here in a easy and efficient way

You can do the following
1)    Create Sub site/pages/files
2)    Delete Sub sites/ pages/ files
3)    Move files between libraries
4)    Delete Sites/ files
5)    Bulk Check in/ Checkout/ Approve pages or documents
6)    Publish Pages – If you want to publish the file, you have to check in the file then approve and then publish it You can do this in one step by selecting the Action >> Publish through Site Content and Structure Page.

Navigation Path: Site Actions >> Manage Content And Structure

Create Site:

Delete Site and its Sub sites (Note: The site will be deleted directly without moving to recycle bin)

Check in, Check Out, Publish

In Internet facing websites, you don’t want anonymous users to access pages such as AllItems.aspx etc. There is a Sharepoint feature ViewFormPagesLockDown which can be enabled to secure your sites. Find out more details about this feature at: http://technet2.microsoft.com/Office/en-us/library/f507f5d6-4c9d-4f98-909f-069c53b9a3f61033.mspx#section6

Activate Feature:
stsadm -o activatefeature -url <site collection url> -filename ViewFormPagesLockDown\feature.xml

De-Activate Feature:

stsadm -o deactivatefeature -url <site collection url> -filename ViewFormPagesLockDown\feature.xml

1) Best Practices: Common Coding Issues When Using the SharePoint Object Model
http://msdn.microsoft.com/en-us/library/bb687949.aspx

2) Best Practices: Using Disposable Windows SharePoint Services Objects
http://msdn2.microsoft.com/en-us/library/ms473633.aspx