1. I assume you already know how to create your own WebParts in SharePoint and is looking for some way to create a property for
   

that WebPart that you can easily Set and Get from your application, like the one on the image below:

 

1. First, on your WebPart class (yellow highlight), and not the User Control class (green highlight), define your properties:
   

   
   

2. For this example, I will show you how to define a text, boolean, integer, date/time, and enumeration property:
   

[ToolboxItemAttribute(false)]

public
class Sample_Web_Part : WebPart

{

// Visual Studio might automatically update

// this path when you change the Visual Web Part project item.

private
const
string _ascxPath =

@”~/_CONTROLTEMPLATES/Sample_Project/” +

@”Sample Web Part/Sample Web PartUserControl.ascx”;

 

protected
override
void
CreateChildControls()

{

Control control = Page.LoadControl(_ascxPath);

Controls.Add(control);

}

 

public
static
Boolean SampleBoolean;

[Category("Extended Settings"),

Personalizable(PersonalizationScope.Shared),

WebBrowsable(true),

WebDisplayName("Sample Boolean"),

WebDescription("Please Choose a Sample Boolean")]

public
Boolean _SampleBoolean

{

get { return SampleBoolean; }

set { SampleBoolean = value; }

}

 

public
static
string SampleText;

[Category("Extended Settings"),

Personalizable(PersonalizationScope.Shared),

WebBrowsable(true),

WebDisplayName("Sample Text"),

WebDescription("Please Enter a Sample Text")]

public
string _SampleText

{

get { return SampleText; }

set

{

// Sample Validation

Regex oRegEx = new Regex(“[a-zA-Z]+”);

if (!oRegEx.IsMatch(value))

throw
new Microsoft.SharePoint.WebPartPages.

WebPartPageUserException(

“Please enter alphabeth characters only”);

SampleText = value;

}

}

 

public
static
int SampleNumber;

[Category("Extended Settings"),

Personalizable(PersonalizationScope.Shared),

WebBrowsable(true),

WebDisplayName("Sample Number"),

WebDescription("Please Enter a Sample Number")]

public
int _SampleNumber

{

get { return SampleNumber; }

set { SampleNumber = value; }

}

 

public
static DateTime SampleDate;

[Category("Extended Settings"),

Personalizable(PersonalizationScope.Shared),

WebBrowsable(true),

WebDisplayName("Sample Date"),

WebDescription("Please Enter a Sample Date")]

public DateTime _SampleDate

{

get { return SampleDate; }

set { SampleDate = value; }

}

 

public
enum CityEnum { Manila, Berlin, Auckland, Zurich };

public
static CityEnum SampleDropDown;

[Category("Extended Settings"),

Personalizable(PersonalizationScope.Shared),

WebBrowsable(true),

WebDisplayName("Sample Drop Down"),

WebDescription("Please Choose a Sample DropDown")]

public CityEnum _SampleDropDown

{

get { return SampleDropDown; }

set { SampleDropDown = value; }

}

}

1. If you notice, each property you create has attributes:
   

• Category – This will group your property according to category. If not declared, “Miscellaneous” will be used as the default.
  
• Personalizable – How the WebPart is configured, which can be per-user (PersonalizationScope.User), or for everyone (PersonalizationScope.Shared). For this example, we have chosen all users.
  
• WebBrowsable – This will hide or show the property on the tool pane.
  
• WebDisplayName – Label for the property.
  
• WebDescription – Description for the property.
  

1. You might also notice that we have validation on the codes. You can add your own like the one on the SampleText
   property where we implemented a Regular Expression, or even in SampleNumber. It is by default validated by its type so you cannot save once it has illegal values.
   

   
   

2. So the final step is consuming that property in your WebPart; you can do it easily like:.
   

   
   

 

Introduction

In SharePoint 2010 you now have the ability to use LINQ syntax to fetch items from your lists instead of using the “traditional” approach of CAML queries. (Including SPSiteDataQuery and SPQuery objects)

LINQ to SharePoint!

In order to work with LINQ in SharePoint 2010, we need use a tool called SPMetal.exe which resides in the 14bin folder. This tool is used to generate some entity classes which Visual Studio 2010 can use to get IntelliSense, and allows for LINQ-based queries to be performed on your lists.

• LINQ to SharePoint queries are translated to proper CAML queries
  
• CAML queries are in turn later translated to SQL queries
  

SPMetal.exe

Using the tool called SPMetal, we generate our entity-classes that are needed to perform these object oriented queries toward our SharePoint server.

These are the required steps to get hooked up:

1. Launch a cmd-window and navigate to C:Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\bin
   
   
   1. Run the following command to utilize the SPMetal.exe tool with the following syntax:
      
      1. spmetal.exe /web:http://nexus-l6:503 /code:c:\EntityModuleSharePoint.cs /user:nexus-l6\nexus /password:XXXXXXX
         /namespace:EntityModuleSharePoint
         
      2. Example:
         

   
   

    

   1. Now navigate to C: (or wherever you chose to output your file) and make sure the file has been generated
      

1. Open up the file and take a look at the content that SPMetal now have provided us with:
   

   
   

Note that the class name is now EntityModuleSharePointDataContext. It’s based on the name you specify as your code file in the SPMetal.exe command line tool.

If you were to use /code:C:\EntityModuleSharePoint.cs instead, it would generate a class called EntityModuleSharePointDataContext.

 

1. Visual Studio 2010 – Let’s create a sample Web Part that utilizes LINQ to SharePoint
   

   1. Create a new project (I’m going to create a new Visual Web Part project)
      
   2. Import your DataContext-file by choosing your Project -> Add -> Existing Item:
      
   3. Specify your file (mine is called EntityModuleSharePoint.cs):
      
   4. Make sure it’s properly placed in your project structure – then we’re good to go:
      

       

   
   

 

 

 

 

 

 

 

   Â
 

 

 

1. Add proper references

   Now in order to use LINQ to SharePoint, you also need to reference the Microsoft.SharePoint.Linq assembly.

   Point to references, right-click and choose “Add Reference” and select the Microsoft.SharePoint.Linq.dll file:

 

1. In your code, reference the assemblies:
   

   
   

2. Code Sample
   

   
   

    

3. Output:
   

   
   

 

1. Drag and drop Telerik.Web.UI.dll and Telerik.Web.Design.dll into C:\Windows\Assembly (in Windows Explorer) & reset IIS
   

    

2. Go to Web.config file of Running Site; add this tag under <controls>
   

    

<add tagPrefix=”asp” namespace=”System.Web.UI.WebControls” assembly=”System.Web.Extensions, Version=3.5.0.0, Culture=neutral,

PublicKeyToken=31BF3856AD364E35″/>

 

 

 

 

1. Find <SafeControls> & add this tag under <SafeControls>
   

 

<SafeControl Assembly=”Telerik.Web.UI, Version=2011.3.1115.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4″

Namespace=”Telerik.Web.UI” TypeName=”*” Safe=”True” />

 

 

 

 

 

 

 

1. In Master Page
   
   1. Register control
      

    

   <%@ register tagprefix=”telerik” namespace=”Telerik.Web.UI” assembly=”Telerik.Web.UI,
   

   Version=2011.3.1115.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4″ %>
   

   
   

    

   1. Change Navigation control
      

   <telerik:RadMenu ID=”RadMenu1″ runat=”server” DataSourceID=”topSiteMap” EnableRoundedCorners=”true” EnableShadows=”true”/>
   

    

   
   

 

1. OUT PUT