Life inside MOSS » Object Model

Accessing Lists through Sharepoint Object model

Geek — Sat, 27 Jun 2009 12:39:37 +0000

Is accessing the list taking more time…

Consider the following while accessing the list through Object model

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.
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.

Understand Sharepoint using Dot Net Reflector

Geek — Sat, 28 Feb 2009 20:57:37 +0000

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.

Sharepoint Object Model Best Practices

Geek — Mon, 14 Jul 2008 18:46:01 +0000

Follow the below best practices while doing custom coding using sharepoint object model. I found these articles very useful.

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