SharePoint & .Net quick samples & tricks

CRUD OPERATIONS USING SHAREPOINT 2013 RESTAPI & ANGULARJS (PART3)

2015-12-29T16:25:00.000+02:00

First let's recap what we do in Part1 which we made an overview about technology used then we explain details about design then we finished Part2 by design all generic JavaScript we will use and layouts , all of these steps made to achieve the example below

i'm an employee in company and need to request vacation so i will log into sharepoint with my account and fill form then send vacation request , i need to see process flow where it located now or who is responsible for take an action for my task now, in other side if i'm employee who has this task now i need to respond on this task.

In this part we will implement lists that we will save data on it then we will implement both controllers.js and services.js for vacation module to finish our Demo :)

To implement our demo we will create sharepoint list "VacationType" to store all types of vacations and "EmployeeVacation" to store submitted employee vacation.

First we will create our sharepoint lists please follow following steps :

create sharepoint project "Demo.Employee".
add new list item "VacationType"
add new list item "EmployeeVacation"

add fields below to list :

DateFrom : date time field to store vacation start date.
DateTo: datetime field to store vacation end date.
VacationType: lookup field to "VacationType" list to set type of vacation.

add event receiver to list to show MyTasks functionality in our demo in this event receiver we will assign task to logged in user once item added , you can replace event receiver with your workflow process if you have.

code to assign task to logged in user

add mapped folder to sharepoint Style Folder then create folders like image below :

services folder will contains all angular employee services

create "EmployeeVacationService.js"

contain all angular controller functionality to add new vacation request.

create "VacationTypeService.js"

get data from vacation type sharepoint list

controllers folder will contains all angular employee controllers.

create "AddEmployeeVacationController.js"

functionality for add employee vacation request.

create "AssignedEmployeeVacationController.js"

controller to get all tasks assigned to current logged in user

create "DetailsEmployeeVacationController.js"

controller to show all details about selected vacation request.

create "MyEmployeeVacationController.js"

controller to get all vacations requested by current logged in user.

create "ProcessEmployeeVacationController.js"

controller to show the current process status of selected vacation.

create visual webPart(farm solution) "EmployeeVacationWebPart" to render views

open "EmployeeVacationWebPartUserControl.ascx"

add all file references to webpart like below :

create "Pages" folder

add module "EmployeePagesModule"
this module consist of page that register webpart created before on it.

delete sample.txt
add "Management.aspx" page to module

open page and write our magic code :

update Element.Xml with code below :

Finally we Finished our demo with complete step by step implementation , if you have any question you're welcome anytime .

CRUD OPERATIONS USING SHAREPOINT 2013 RESTAPI & ANGULARJS (PART2)

2015-12-04T14:47:00.000+02:00

As we discussed in Part1 we talked about why we going to use Angularjs with Sharepoint then we decided to explain our topic by demo

i'm an employee in company and need to request vacation so i will log into sharepoint with my account and fill form then send vacation request , i need to see process flow where it located now or who is responsible for take an action for my task now, in other side if i'm employee who has this task now i need to respond on this task.

Check Final result of Demo that we will do it now.

NO PAGE LOADING ANY MORE :)

now we will start with first point which is "Build Angularjs Structure" , actually we have many type of structure when we start to use Angularjs but i prefer to use following structure but feel free to use your own :

Example :

Demo "folder under Styles SharePoint mapped folder"

Employee "folder container"

controllers "folder container"

AddEmployeeController.js "controller file"

services "folder container"

EmployeeServices.js "services file"

App.js "main angularjs file"
Directives.js "common directive file"
Messages.js "file contain all common messages you will use in your project"
services "folder contain most common service over project"

utility.js " common service file can use over project"

Demo "folder under Layouts SharePoint mapped file"

add.html "view model"

and now we will start our demo , open your visual studio :D :D

we will create 2 projects one for common functions and other specific for employee functionality.

first step we will create general services that we will use it over sharepoint

1- create empty SharePoint project "Demo.CommonUI" as farm solution

2- create folder "Demo" under STYLES mapped SharePoint folder (Templates > Layouts > Styles)

3- create folder "Vendor" under demo folder

we will add add library will be used in our demo under this folder.

add Angularjs framework files under this folder you can download it through this link ,

actually i will use CDN links in my demo to save time., here is some prerequisite libraries we will use in our project :

jquery
Angularjs : for angularjs functionality
ng-table : for draw tables with full functionality (feel free to use your own library)
toaster : for show notification after api response.
loader : for show loader if request required time.
UIBootstrap : for boot strap controls

my current vendor now will contain only files for "loader" and i will use CDN for other libraries

so project now will look like:

4- create some common files under "Demo" folder :

create "app.js" :

in code below we will handle routing of views and it's mapped controllers also we will add configuration for loader and inject all libraries that we will use in our project

create "Directives.js":

we will use it to create our own directives to use it in views, in code below i will use my custom datepicker and validation to validate FromDate & ToDate when employee submit vacation

create "Messages.js":

we will use it centralize out used messages accross system

create folder "services":

create "baseSvc.js"

this file one of the most important files in our project here we will add all method GET,POST that will call SharePoint RestApi.

create "UtilityService.js"

if you have any common function you can add it in utility.

5- now we need to create our views for all CRUD operations.

Add "Layouts" SharePoint mapped folder

create folder "EmployeeVacation" under "Demo.commonUI" folder add following files :

create "add.html" that will appear when employee need to request vacation

create "details.html" to show details about request.

create "MyRequests.html" to show all requests created by logged in user.

create "MyTasks.html" to show all tasks assigned to logged in user

create "process.html" to show current task status

6 - At last we are going to create our page layout

create folder "PageLayouts"

under folder create module "PageLayouts"

delete sample.txt
add text file "DemoManagementPageLayout.aspx" then add magic code below :
update file "Elements.xml" with code below :

Finally we finished CommonUI Structure, congratulations :D .

in Part3 we will talk about Build Back end Structure of SharePoint and angular business layer

CRUD Operations using Sharepoint 2013 RestApi & Angularjs (Part1)

2015-12-01T22:15:00.000+02:00

On first time joined my new job and client have only one issue with SharePoint which is staff decided to never use this portal until it come more faster, so we made a long meeting and finally we decided to use powerful of SharePoint functionality and on the same time use powerful of client side framework like Angularjs , from first time we knew that we will face some of challenges as when we start study and make a lot of search of how to implement Angularjs module with SharePoint RestAPI we have not a lot of references talk about it ,most of developers use knockout as client side with SharePoint so we need to take care while design our project in case that anytime we face some issues can't implemented with Angular we can use alternative way to do it even by CSOM "Client Side Object Model" and finally we made full designed structure you can use if you think to try use SharePoint and Angularjs.

I know it's long introduction but i have to explain to you what's reason that forced us to follow this strategy. And now it's time to begin ,for me the best way to learn something is to have full demo and here we are, this blog will divide into 3 parts;

Build Angularjs Structure.
Build Back end Structure of SharePoint and angular business layer
Build generic UI project as front end interface for our demo.

now lets explain our demo will be like that :

i'm an employee in company and need to request vacation so i will log into sharepoint with my account and fill form then send vacation request , i need to see process flow where it located now or who is responsible for take an action for my task now, in other side if i'm employee who has this task now i need to respond on this task.

That's it so simple example we will start step by step on this demo to cover all business process.

And here we go, stay tuned for Part2

Exporting the XSLT List View Web Part in SharePoint 2010

2014-03-16T15:09:00.000+02:00

you can’t export a XSL list view web part.

As you can see in the above screenshot the ability to export an XLV has been disabled by default – but that is something that you can pretty easily turn back on. Admittedly at some point here SPD has was used for the following technique – but once it’s been used (i.e. once only by me) there’s no reason that you’ll ever need it to use it again once you have the following few lines of mark-up (i.e. you don’t need it!).

So, my approach involved opening up a page with an XLV in SPD and saving the web part file locally. I then simply edited the resulting file in notepad until it looked like the below code:

<?xml version="1.0" encoding="utf-8" ?><webParts> <webPart xmlns="http://schemas.microsoft.com/WebPart/v3"> <metaData> <type name="Microsoft.SharePoint.WebPartPages.XsltListViewWebPart, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> <importErrorMessage>Cannot import this Web Part.</importErrorMessage> </metaData> <data> <properties> <property name="ListUrl" type="string">Lists/CustomList</property> <property name="ExportMode" type="exportmode">All</property> </properties> </data> </webPart></webParts>

With this code I can carry out the following steps to give me an XLV that can be exported:

Modify the ListUrl property to the site relative url of my list
E.g. note here that in my example it is lists/customlist not /subsite/lists/customlist
Save the file locally with an appropriate filename and the extension .webpart
Edit a page on the same site* as the list and upload this web part

4. Add the web part to the page – and note the option to export is now available!

5. You should now be able to edit this web part just like any other XLV, e.g. modifying the view etc.

Now that we have the ability to export an XLV it is the first step in opening up some of those great features that are available in SPD for those situations where it’s simply not possible to use SPD itself.

*As a final thought, this works for an XLV on the same site as the list you want to show – but what about if you wanted to show a list from a different site? Well, I think in this case you could replace the ListUrl property with the ListId and the WebId properties and that may work for you. When I get a moment I’ll confirm this.

SharePoint 2010 Breadcrumb not showing sub folders in document library

2014-03-16T14:59:00.005+02:00

SharePoint 2010 Breadcrumb not working sub folders in document library

Solution
1. Open site in SharePoint designer 2010
2. Open “All Files” à Select Document Library from the list à Forms à AllItems.aspx
3. Open “AllItems.aspx” in SharePoint Designer ( select code view )
4. Find out “<asp:Content ContentPlaceHolderId="PlaceHolderPageTitleInTitleArea" runat="server">”
5. Change the code
" <SharePoint:ListProperty Property="Title" runat="server"/> "
To

<SharePoint:ListProperty Property="TitleBreadcrumb" runat="server"/>
<SharePoint:UIVersionedContent UIVersion="4" runat="server">
<ContentTemplate>
<span class="ms-ltviewselectormenuheader" runat="server">
<SharePoint:ListTitleViewSelectorMenu AlignToParent="true" id="LTViewSelectorMenu" runat="server" />
</span>
</ContentTemplate>
</SharePoint:UIVersionedContent>
</asp:Content>
6. Save the file
7. Refresh the SharePoint page

Creating a custom Page Layout based on ContentType in SharePoint 2010

2014-03-16T14:56:00.002+02:00

First, open Visual Studio and create a new C# project, using the "Empty SharePoint Project" template, listed under the SharePoint 2010 project templates. For this example, we'll name our project "MyCustomPageLayout".

For this example, we'll be deploying our solution as a "Farm solution".

Click "Finish" to wire up your solution to your particular SharePoint site.

Content Type

First thing to do is to define a content type.
I will call my Content Type: PicturePageContentType

To do this:
- Go to: Site Settings –> Site content types
- Next, click Create

In the following screen you insert information about the content type.
An import thing to do is let it inherit from the right parent content type.
This needs to be from the group: Publishing Content Types and the parent needs to be Page.

So far nothing special, next I added some non existing columns.
On the following page click Add from new site column.

Define in the screen the follows up the columns that you would like to add to the your content type (Page Layout in the end).

After you added all the columns you needed you can overview it when you’re looking at you content type. You’ll see that I added Page Content, this was one from the already existing site columns.

Note: If you added a from column to your page you cannot delete it:) If you want to get rid of it you need to delete the whole content type.

Create the Page Layout

As with SharePoint 2007, we'll need to provision our Page Layouts to our SharePoint Site Collection Master Page Gallery by using a "Module" element. To do this, right click on the Project and say you want to add a new item. Select "Module" from the list of SharePoint 2010 items.

We'll name the Module "masterpage". When you create the new module, you'll see something like this:

By default, the module contains a sample text file you, so you can see how the Module deploys a file to SharePoint. However, we don't need it, so we'll delete Sample.txt. Next, we need to wire up our module to point to the URL of the Master Page Gallery, so we'll add a "Url" attribute to the Module node. Our Elements.xml file should now contain this XML:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Module Name="masterpage" Url="_catalogs/masterpage">
</Module>
</Elements>

Next, we're going to drop our new Page Layout file into the Module. To do this, we'll right-click on the "masterpage" module in the Visual Studio explorer and select "Add new item". We're once again presented with the "Add New Item" dialog. If we were to select "Application Page" from the SharePoint 2010 menu, we'd get a code-behind page in addition to our ASPX page, which we don't want. Since all we want to provision is markup (and not code), we're going to use a shortcut. Select the "General" node and select "Text File" from the list of items. However, name the file "MyCustomPageLayout.aspx".

Add your Page Layout markup into your MyCustomPageLayout.aspx page. You can do it how I do it, which is to create a new Page Layout in SharePoint designer,

Now, we need to add the code for PageLayout1.aspx. It's easier to design for the page first in SharePoint designer and then cop the code over.

So let's open SharePoint designer to the site you are developing on. Select "Page Layouts" under Site Objects.

In the ribbon click "New Page Layout". In the dialog box select Custom Content Types and ContentType1. Enter a URL Name and Title

In the Toolbox, under SharePointControls, Server Controls, Content Fields you should see PageContent and PageImage. Drag these two fields onto the page in the "PlaceHolderMain" content area so it looks like this

Once again, the FieldName values most likely won't match yours since that's a guid generated by the system. We will make two changes before we copy the code over to our project. Instead of leaving the guid for the field names we will change the FieldName to the actual names of the fields -- PageContent and PageImage so the code will be

<PublishingWebControls:RichImageField FieldName="PageImage" runat="server"></PublishingWebControls:RichImageField>

<PublishingWebControls:RichHtmlField FieldName="PageContent" runat="server"></PublishingWebControls:RichHtmlField>

This makes it easier when deploying the solution to dev, staging, and production since the FieldName guids rarely match when moving to a different SharePoint 2010 environment.

Also, in the Page directive at the top of the page get rid of the following text: meta:webpartpageexpansion="full" meta:progid="SharePoint.WebPartPage.Document"

Take the code from the DesignPageLayout and copy it over to the PageLayout1.aspx page in your project.

then copying the code to Visual Studio. However, DO NOT FORGET to remove the attributes in the Page Directive at the top of the page that SharePoint Designer adds, that look like this:

meta:webpartpageexpansion="full" meta:progid="SharePoint.WebPartPage.Document"

If you don't forget to remove those items from the Page directive, SharePoint will think your pages have been customized, even though they were deployed via a Feature.

Next, we'll need to update the Module's Elements.xml file to tell SharePoint what to do with the new Page Layout.

The first thing we'll need to do is to update the "Url" property of the File element, by removing the "masterpage/" prefix fromt the Url. (Since we already specified in the Module element that we're deploying the Page Layout to the "masterpages" library, if we left the "masterpages/" part of the Url on the file, SharePoint would try to provision our Page Layout into a library called "masterpages" inside the existing "masterpages" library! We don't want that!) Your new File element should look like this:

<File Path="masterpage\MyCustomPageLayout.aspx" Url="MyCustomPageLayout.aspx" />

Now we need to specify some properties for the Page Layout. These properties are identical to the kind of properties you would specify for a Page Layout in SharePoint 2007:

The Title of the file in SharePoint
In our case, the file itself has a URL of MyCustomPageLayout.aspx, but we can also give the page a Title that will show up when the Page Layout is being selected by the content author, such as "My Custom Page Layout".
The Content Type
All Page Layouts must inherit from the "Page Layout" content type (which we add using a Resource file value.)
A Publishing Preview Image
The Publishing Preview Image is the image that shows up when a user picks that Page Layout from the Page Layout picker while they're creating a new page. In this example, we'll just point to the Article Page's preview image.
The Publishing Associated Content Type
This is the Content Type that the Page Layout is representing, such as an "Article Page", "Welcome Page", etc. The value is a string representing a Lookup value that's a combination of the name of the Content Type and its unique identifier.

Our new File node will look like this:

<File Path="masterpage\MyCustomPageLayout.aspx" Url="MyCustomPageLayout.aspx" Type="GhostableInLibrary">
      <Property Name="Title" Value="My Custom Page Layout" />
      <Property Name="ContentType" Value="$Resources:cmscore,contenttype_pagelayout_name;" />
      <Property Name="PublishingPreviewImage" Value="~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/CustomPageLayout.png, ~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/CustomPageLayout.png" />
      <Property Name="PublishingAssociatedContentType" Value=";#ContentTypeName;
#0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D;#"
/>
</File>

Please note, there's no line break inside the PublishingAssociatedContentType value string; I needed to add a line break so you could see the whole value here.

That's it! We've built our Module.

Now, we're going to add a module for the Page Layout preview image. Right click on the project and add an additional Module element. Delete the "Sample.txt" file from it, and add your new preview image. (In our case, we'll call it CustomPageLayout.png".) Modify your module file so it looks like this:

<Module Name="Previews Images" Url="_catalogs/masterpage/$Resources:core,Culture;/Preview Images">
  <File Path="Preview Images\CustomPageLayout.png" Url="CustomPageLayout.png" Type="GhostableInLibrary">
      <Property Name="Title" Value="Custom Page Layout Preview Image" />
  </File>
</Module>

You might have noticed that a new Feature got created for you when you created a new Module. Let's rename the Feature itself MyCustomPageLayout in the project tree, like this:

We'll open up our MyCustomPageLayout feature, and give it a helpful name and description. Notice that you can graphically see that your Module is a part of this Feature, and you can even see which Module files will be provisioned when the Feature is activated.

The last thing we need to do is to make sure our Solution Package is getting configured correctly, to include our new Feature.

By default, the "Empty SharePoint Project" will create a DLL for you. If we just went ahead and deployed our Solution Package with the settings as-is, we would be deploying a DLL to the GAC. However, since our solution doesn't have any code in it, it would be a blank DLL. That's a bit messy, so let's avoid that. Click on the Project in your Solution Explorer, and look in the Properties Window. Change the "Include Assembly in Package" property to "False".

Important note: This value is in the Properties Window. I was originally looking for it in the Properties page of the Project (say that three times fast), and I couldn't find it there.

To deploy our new Solution Package to our Sandboxed Site, we'll go to the "Build" menu in Visual Studio, and select "Deploy MyCustomPageLayout".

This will assemble the Solution Package, deploy the Solution Package to the Sandbox, then activate the Sandboxed feature.

If we browse to our Master Page Library, we'll now see our new Page Layout. Note that, unlike SharePoint 2007, our Page Layout will appear checked out by default, if we haven't modified any of the approval or check-out settings of the out of the Master Page Gallery. We'll need to check it in and approve it for it to be available to us.

Refrences:

Links :

http://rburgundy.wordpress.com/2010/05/21/sharepoint-2010-create-page-layout-based-on-a-custom-content-type-in-visual-studio-2010/

http://www.rkinteractive.com/blogs/SoftwareDevelopment/post/2012/01/06/Creating-Custom-Content-Types-and-Page-Layouts-in-Visual-Studio-2010.aspx

http://www.c-sharpcorner.com/Forums/Thread/182458/how-to-create-page-layout-in-sharepoint-2010-using-visual-st.aspx

Error on start & end tag Page Directive ..SharePoint2010

2014-03-16T14:37:00.001+02:00

if you face problem on tag page directive all what you need to do is Close & Open File :) , simple right ! :D

Fix for 'Load control template .. TaxonomyPicker.ascx"

2014-03-16T14:35:00.000+02:00

if you face problem in TexonomyPicker.ascx , please follow link below have solution :

o http://gallery.technet.microsoft.com/office/32d06697-ab7f-447e-9d0e-b6d93bee3fda

Error occurred in deployment step 'Retract Solution': Cannot start service SPUserCodeV4 on computer

2014-03-16T14:33:00.006+02:00

- When i got this error i searched in net and found a solution to enable Microsoft Sharepoint foundation User Code Service in services section of Central Administration. Unfortunately i couldnt find a service with that name.

- While searching in services.msc i found that SharePoint 2010 User Code Host was not started. Once the Service was started the issue got resolved.

Download Document on click in Document Library

2014-03-09T13:22:00.002+02:00

Default behavior in SharePoint is to open display view form on click to an item on document library , if you need to download document item instead of view it we need to have workaround .

in this example we only download documents with extensions ".doc,.docx,.xls,.xlsx,.ppt,.pptx,.pdf"

Follow steps below to change behavior to download document :
- open document library and add content query web-part .
- Edit web-part as HTML.
- add the following code :

$(function () {

var extensions = ".doc,.docx,.xls,.xlsx,.ppt,.pptx,.pdf";

$(".srch-Title3 a").each(function () {

var hrefDoc = $(this).attr('href');

var fileExt = hrefDoc.substring(hrefDoc.lastIndexOf('.'), hrefDoc.length);

if (extensions.toString().toLowerCase().indexOf(fileExt) != -1) {

this.href = '/_layouts/download.aspx?SourceURL=' + this.href;

}

});

$("a[onclick*='DispEx']").each(function (data) {

var fileExtIndex = this.toString().lastIndexOf('.');

var fileExt = this.toString().substr(fileExtIndex);

var index = extensions.toString().indexOf(fileExt);

if (extensions.toString().toLowerCase().indexOf(fileExt) != -1) {

var href = this.href;

this.href = '/_layouts/download.aspx?SourceURL=' + this.href;

$("a[onclick*='DispEx']").removeAttr('onclick');

$("a").removeAttr('onmousedown');

}

});

$("a[onclick*='DispDocItemExWithServerRedirect']").each(function (data) {

var fileExtIndex = this.toString().lastIndexOf('.');

var fileExt = this.toString().substr(fileExtIndex);

var index = extensions.toString().indexOf(fileExt);

if (extensions.toString().toLowerCase().indexOf(fileExt) != -1) {

var href = this.href;

this.href = '/_layouts/download.aspx?SourceURL=' + this.href;

$("a[onclick*='DispDocItemExWithServerRedirect']").removeAttr('onclick');

$("a").removeAttr('onmousedown');

}
});

Creating a custom Page Layout in SharePoint 2010

2013-06-08T21:16:00.000+02:00

Creating a custom Page Layout in SharePoint 2010 is not too different than creating a custom Page Layout in SharePoint 2007. However, the process of creating a SharePoint Solution Package has changed in Visual Studio 2010. This article will walk you through the steps.

First, open Visual Studio and create a new C# project, using the "Empty SharePoint Project" template, listed under the SharePoint 2010 project templates. For this example, we'll name our project "MyCustomPageLayout".

For this example, we'll be deploying our solution as a "Farm solution".

Click "Finish" to wire up your solution to your particular SharePoint site.

Content Type:

First thing to do is to define a content type.
I will call my Content Type: PicturePageContentType To do this: -

- Go to: Site Settings –> Site content types
- Next, click Create

So far nothing special, next I added some non existing columns.
On the following page click Add from new site column.

Define in the screen the follows up the columns that you would like to add to the your content type (Page Layout in the end).

After you added all the columns you needed you can overview it when you’re looking at you content type. You’ll see that I added Page Content, this was one from the already existing site columns.

<Field ID="{7169882F-9B0C-4EA8-A096-9822C720D3BB}" Name="PageContent" DisplayName="PageContent" Type="HTML" RichText="TRUE" RichTextMode="FullHtml" /> <Field ID="{ECD16AAB-CEA3-4D0A-9F48-16F59B29C73A}" Name="PageImage" DisplayName="PageImage" Type="Image" RichText="true" />

Note: If you added a from column to your page you cannot delete it:) If you want to get rid of it you need to delete the whole content type.

Create the Page Layout

As with SharePoint 2007, we'll need to provision our Page Layouts to our SharePoint Site Collection Master Page Gallery by using a "Module" element. To do this, right click on the Project and say you want to add a new item. Select "Module" from the list of SharePoint 2010 items.

We'll name the Module "masterpage". When you create the new module, you'll see something like this:

<?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Module Name="masterpage" Url="_catalogs/masterpage">
</Module>
</Elements> <Module Name="masterpage" Url="_catalogs/masterpage"> </Module> </Elements>

Next, we're going to dop our new Page Layout file into the Module. To do thhis, we'll right-click on the "masterpage" module in the Visual Studio explorer and select "Add new item". We're once again presented with the "Add New Item" dialog. If we were to select "Application Page" from the SharePoint 2010 menu, we'd get a code-behind page in addition to our ASPX page, which we don't want. Since all we want to provision is markup (and not code), we're going to use a shortcut. Select the "General" node and select "Text File" from the list of items. However, name the file "MyCustomPageLayout.aspx". Add your Page Layout markup into your MyCustomPageLayout.aspx page.

You can do it how I do it, which is to create a new Page Layout in SharePoint designer,

Now, we need to add the code for PageLayout1.aspx. It's easier to design for the page first in SharePoint designer and then cop the code over.
So let's open SharePoint designer to the site you are developing on. Select "Page Layouts" under Site Objects.

In the ribbon click "New Page Layout". In the dialog box select Custom Content Types and ContentType1. Enter a URL Name and Title

the FieldName values most likely won't match yours since that's a guid generated by the system. We will make two changes before we copy the code over to our project. Instead of leaving the guid for the field names we will change the FieldName to the actual names of the fields -- PageContent and PageImage so the code will be

<PublishingWebControls:RichImageField FieldName="PageImage" runat="server"></PublishingWebControls:RichImageField><PublishingWebControls:RichHtmlField FieldName="PageContent" runat="server"></PublishingWebControls:RichHtmlField>

This makes it easier when deploying the solution to dev, staging, and production since the FieldName guids rarely match when moving to a different SharePoint 2010 environment.

Also, in the Page directive at the top of the page get rid of the following text: meta:webpartpageexpansion="full" meta:progid="SharePoint.WebPartPage.Document"

Take the code from the DesignPageLayout and copy it over to the PageLayout1.aspx page in your project.

then copying the code to Visual Studio. However, DO NOT FORGET to remove the attributes in the Page Directive at the top of the page that SharePoint Designer adds, that look like this:

meta:webpartpageexpansion="full" meta:progid="SharePoint.WebPartPage.Document"

If you don't forget to remove those items from the Page directive, SharePoint will think your pages have been customized, even though they were deployed via a Feature.

Next, we'll need to update the Module's Elements.xml file to tell SharePoint what to do with the new Page Layout.

The first thing we'll need to do is to update the "Url" property of the File element, by removing the "masterpage/" prefix fromt the Url. (Since we already specified in the Module element that we're deploying the Page Layout to the "masterpages" library, if we left the "masterpages/" part of the Url on the file, SharePoint would try to provision our Page Layout into a library called "masterpages" inside the existing "masterpages" library! We don't want that!) Your new File element should look like this:

<File Path="masterpage\MyCustomPageLayout.aspx" Url="MyCustomPageLayout.aspx" />

Now we need to specify some properties for the Page Layout. These properties are identical to the kind of properties you would specify for a Page Layout in SharePoint 2007:

• The Title of the file in SharePoint In our case, the file itself has a URL of MyCustomPageLayout.aspx, but we can also give the page a Title that will show up when the Page Layout is being selected by the content author, such as "My Custom Page Layout".
• The Content Type All Page Layouts must inherit from the "Page Layout" content type (which we add using a Resource file value.)
• A Publishing Preview Image The Publishing Preview Image is the image that shows up when a user picks that Page Layout from the Page Layout picker while they're creating a new page. In this example, we'll just point to the Article Page's preview image.
• The Publishing Associated Content Type This is the Content Type that the Page Layout is representing, such as an "Article Page", "Welcome Page", etc. The value is a string representing a Lookup value that's a combination of the name of the Content Type and its unique identifier.

Our new File node will look like this:

<File Path="masterpage\MyCustomPageLayout.aspx" Url="MyCustomPageLayout.aspx" Type="GhostableInLibrary"> <Property Name="Title" Value="My Custom Page Layout" /> <Property Name="ContentType" Value="$Resources:cmscore,contenttype_pagelayout_name;" /> <Property Name="PublishingPreviewImage" Value="~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/CustomPageLayout.png, ~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/CustomPageLayout.png" /> <Property Name="PublishingAssociatedContentType" Value=";#ContentTypeName;#0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D;#" /> </File>

Please note, there's no line break inside the PublishingAssociatedContentType value string; I needed to add a line break so you could see the whole value here.

That's it! We've built our Module.

Now, we're going to add a module for the Page Layout preview image. Right click on the project and add an additional Module element. Delete the "Sample.txt" file from it, and add your new preview image. (In our case, we'll call it CustomPageLayout.png".) Modify your module file so it looks like this:

<Module Name="Previews Images" Url="_catalogs/masterpage/$Resources:core,Culture;/Preview Images">

<File Path="Preview Images\CustomPageLayout.png" Url="CustomPageLayout.png" Type="GhostableInLibrary"> <Property Name="Title" Value="Custom Page Layout Preview Image" /> </File> </Module>

You might have noticed that a new Feature got created for you when you created a new Module. Let's rename the Feature itself MyCustomPageLayout in the project tree, like this:

The last thing we need to do is to make sure our Solution Package is getting configured correctly, to include our new Feature.
By default, the "Empty SharePoint Project" will create a DLL for you. If we just went ahead and deployed our Solution Package with the settings as-is, we would be deploying a DLL to the GAC. However, since our solution doesn't have any code in it, it would be a blank DLL. That's a bit messy, so let's avoid that. Click on the Project in your Solution Explorer, and look in the Properties Window. Change the "Include Assembly in Package" property to "False".

Important note: This value is in the Properties Window. I was originally looking for it in the Properties page of the Project (say that three times fast), and I couldn't find it there.

To deploy our new Solution Package to our Sandboxed Site, we'll go to the "Build" menu in Visual Studio, and select "Deploy MyCustomPageLayout".

This will assemble the Solution Package, deploy the Solution Package to the Sandbox, then activate the Sandboxed feature. If we browse to our Master Page Library, we'll now see our new Page Layout. Note that, unlike SharePoint 2007, our Page Layout will appear checked out by default, if we haven't modified any of the approval or check-out settings of the out of the Master Page Gallery. We'll need to check it in and approve it for it to be available to us.

Refrences: Links :

http://rburgundy.wordpress.com/2010/05/21/sharepoint-2010-create-page-layout-based-on-a-custom-content-type-in-visual-studio-2010/ http://www.rkinteractive.com/blogs/SoftwareDevelopment/post/2012/01/06/Creating-Custom-Content-Types-and-Page-Layouts-in-Visual-Studio-2010.aspx http://www.c-sharpcorner.com/Forums/Thread/182458/how-to-create-page-layout-in-sharepoint-2010-using-visual-st.aspx

Error occurred in deployment step 'Retract Solution': Cannot start service SPUserCodeV4 on computer

2013-06-08T20:41:00.000+02:00

When i got this error i searched in net and found a solution to enable Microsoft Sharepoint foundation User Code Service in services section of Central Administration. Unfortunately i couldnt find a service with that name. While searching in services.msc i found that SharePoint 2010 User Code Host was not started. Once the Service was started the issue got resolved. Fix for 'Load control template... TaxonomyPicker.ascx" http://gallery.technet.microsoft.com/office/32d06697-ab7f-447e-9d0e-b6d93bee3fda Error on start & end tag Page Directive Close & open File

export one library in multiple site

2013-06-05T19:00:00.001+02:00

I will show how to create a custom web part that represents a list or library’s view and use this web part in other sites (at least in the same site collection) without copying documents between sites.
This custom web part supports a tool bar so files can be uploaded and maintained in a single library, but viewed and maintained from any site in the site collection that has this web part.
Tools needed:
- SharePoint Designer (to make one quick change, export the web part, and then optionally roll back the change)
- Some way to find the site’s GUID (see link to a tool below)
First some observations:
- While editing a web part page, click a web part’s menu and you will usually see an Export option, except for list and library web parts.
- List and library view pages are web part pages (they have “Edit Page” in the Site Actions menu") and the displayed list is a web part.
So how can you export a list web part?

Turns out to be pretty easy. Edit the page in SharePoint Designer and change one word.
1. Open the site in SharePoint Designer and double click on a page with the web part (default.aspx, Shared Documents/Forms/Allitems.aspx, etc)
2. In the code view find the web part and find
  <ExportControlledProperties>false</ExportControlledProperties>
  and change from “false” to “true”
3. Save the page (this will “unghost” the page, but you can undo the changes after the export is complete – right-click the file in the Folder List and select Reset to Site Definition)
4. Go to a browser and visit this page. Go to Site Actions, Edit Page.
5. Click Edit in web part you just modified and click Export.
6. Give the file a name and save it somewhere where you can find it in the next step.
To import the exported settings as a new web part:
1. Visit your top level site in the site collection and go to Site Actions, Site Settings, and in the Galleries column click Web Parts
To add the web part.
1. Nothing special here. Add this web part just like any other web part.
Some differences…

Oddly, the displayed columns are different. The AllItems view displayed Type, Name, Modified and Modified By. The new web part displays Type, Name and Modified By. This is easy to fix. Edit the web part and change the Selected View property to All Documents then you will get the same list of columns in both displays.

The new web part does not display a toolbar by default, but this can be enabled from the web part’s properties panel. If the toolbar is enabled you will see all of the buttons found in the AllItems page, New, Upload, Actions and Settings (depending on the current user’s security rights).

Now test the web part in a sub site….

Error!

    Unable to add selected web part(s).
    List does not exist.
    The page you selected contains a list that does not exist.

On the first attempt it appears that the new exported web part will not work on another site. Time for more research…

Find the missing GUID

Open the .DWP (.WEBPART in 2010) file created by the Export. Find these two lines:

SP 2007
   <ListName …..>{ list_guid_here } </ListName>
   <WebId ….> all_zeros_guid_here </WebId>

SP 2010

   <property name="ListName" type="string">{ list_guid_here } </property>
   …
   <property name="WebId" …>all_zeros_guid_here </property>

SharePoint uses Globally Unique IDs (GUIDS) to identify just about everything stored in the databases. Notice that the ListName has a GUID, but the WebId is all zeros. Replace the zeros with the GUID for the site that owns the list and all will then work.

How to find a GUID

I can’t find any place in the the pages exposed in SharePoint Designer where the web site’s GUID is used, although the list’s GUID can be found in some of the URLs (for example after clicking Settings, List or Library Settings). I wrote two little utilities to display a site’s GUIDs, one a Windows application and the other a page you can deploy to the LAYOUTS folder on the server.

See: http://techtrainingnotes.blogspot.com/2009/03/sharepoint-finding-sharepoint-guids.html

Quick note: Internally a site is call a “web” and a site collection is called a “site”. (go figure…) The utilities above use the web and site names.

Update the web part file

Edit the WebId element and replace the all zeros GUID with the site’s GUID:

SP 2007”   <WebId ….> all_zeros_guid_here </WebId>

SP 2010    <property name="WebId" …>all_zeros_guid_here </property>

After updating the DWP file with the site’s (web’s) GUID, re-upload it to the web part gallery and go and test the web part in a sub site.

And for the “Strange Things” list… the GUID for the web site does not include brackets ( { } ) and is in lower case. The GUID for the list must have brackets and MUST be in UPPER CASE or it will not work.

Reference:http://techtrainingnotes.blogspot.com/2009/03/sharepoint-one-library-multiple-sites.html

check if current web is root web or sub web in XSL

2013-06-05T18:52:00.001+02:00

[Code]

<xsl:if test="string-length($WebUrl) = 3"> <a href="Forms/AllNews.aspx?RootFolder=/Pages/News"> <xsl:text disable-output-escaping="yes"> </xsl:text></a> </xsl:if>

All webpart appear as ErrorWebParts when using SPLimitedWebPartManager

2013-06-05T18:42:00.001+02:00

Hi! recently I was given a task to update properties of multiple webparts(custom developed webparts created by extending existing SharePoint OTB webparts).
Now the trick was to fetch those webparts across pages multiple pages and update their properties and UI formatting instructions based on a configuration file which is provided at run time on feature activation.

Seems a simple enough task, where one needs to retreive page-url, fetch SPLimitedWebPart manager based on page-url.
Use SPLimitedWebPart Manager to iterate through collection of webparts which exist of specified page URL and update properties based on configuration input.

Like any other developer, I started of write code to implement this.
Half-way down the line when I began to query webparts collection using SPLimitedWebPart Manger,
I see all webparts returned are of type "ErrorWebParts".

Why? Because of the following code is called by the specific properties of the ContentByQueryWebpart

The webpart will always call the SPContext, there is no web-context. Therefore when initiating the
ContentByQueryWebpart

A workaround for this would be to provide it with a context. all what i do adding if condition before query on
webparts if HttpContetxt is null i'll add it.

[Code]

if (HttpContext.Current == null) { HttpRequest request = new HttpRequest("", web.Url, ""); HttpContext.Current = new HttpContext(request, new HttpResponse(new StringWriter())); HttpContext.Current.Items["HttpHandlerSPWeb"] = web; }
SPFile filePath = webToUpgrade.GetFile("[ path of your page ]");
SPLimitedWebPartManager webpartManager = filePath.GetLimitedWebPartManager(System.Web.UI.WebControls.WebParts.PersonalizationScope.Shared);
SPLimitedWebPartCollection webPartColl = webpartManager.WebParts;
foreach (var webpart in webPartColl) { // write your code }

check current culture language in publishing page

2013-06-05T18:37:00.000+02:00

check current language is Arabic language in publishing page

[Code]

<% if (System.Threading.Thread.CurrentThread.CurrentUICulture.LCID==1025){ %><%}else{%><%}%>

check Publishing page status

2013-06-05T18:33:00.001+02:00

if you want to check current status in publishing page is Display mode :
[Code]

<%if (Microsoft.SharePoint.SPContext.Current.FormContext.FormMode == SPControlMode.Display) { %> <asp:HyperLink runat="server" Text="<%$ Resources: SECITN.ListdefinitionStrings, backToNewsBtn %>" NavigateUrl="javascript:void(0);" OnClick="if($('.breadcrumbNode').length == 1){ $(this).attr('href','../forms/allnews.aspx?RootFolder=/' +$('.breadcrumbNode').attr('href').split('/')[1]+ '/Pages/News')}else{$(this).attr('href','../forms/allnews.aspx?RootFolder=/Pages/News')}"/> <%}%>

All webpart appear as ErrorWebParts when using SPLimitedWebPartManager

2013-06-05T16:49:00.001+02:00

if (HttpContext.Current == null) { HttpRequest request = new HttpRequest("", web.Url, ""); HttpContext.Current = new HttpContext(request, new HttpResponse(new StringWriter())); HttpContext.Current.Items["HttpHandlerSPWeb"] = web; }
SPFile filePath = webToUpgrade.GetFile("[ path of your page ]");
SPLimitedWebPartManager webpartManager = filePath.GetLimitedWebPartManager(System.Web.UI.WebControls.WebParts.PersonalizationScope.Shared);
SPLimitedWebPartCollection webPartColl = webpartManager.WebParts;
foreach (var webpart in webPartColl) { // write your code }

Error occurred in deployment step 'Recycle IIS Application Pool'

2013-03-08T20:12:00.003+02:00

Problem: in a project using SharePoint 2010 and Visual Studio 2010 during a deployment procedure we required to retract some packages before deploy a new version, during this process visual studio suddenly show us the next error:

'Recycle IIS Application Pool': The open operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.

Solution: some times the best solution is find the most easy way, so after trying to restart IIS and try the process again unsuccessfully, the solution is close visual studio, then open the solution and try retract the package one more time .. yeap, believe me it works!! :D

SetMasterAndWelcomePageOn feature activates Programatically

2013-03-08T20:09:00.001+02:00

[Code]

public override void FeatureActivated(SPFeatureReceiverProperties properties)
        {            try            {               SPSecurity.RunWithElevatedPrivileges(delegate                {                    using (var web = properties.Feature.Parent as SPWeb)                    {                        if (web == null) return;
                        web.ValidateFormDigest();                        SetMasterPage(web);                        SetDefaultHomePage(web);                      }                });            }            catch (Exception ex)            {            }            finally            {            }        }
        private static void SetDefaultHomePage(SPWeb varoWeb)        {            try            {   varoWeb.AllowUnsafeUpdates = true;                    SPFolder folder = varoWeb.RootFolder;                    folder.WelcomePage = "Pages/home.aspx";                    folder.Update();                    varoWeb.AllowUnsafeUpdates = false;   }            catch (Exception e)            {    throw new SPException("Error when trying to Set DefaultPage. Error: " + e.Message);            }        }
        private void SetMasterPage(SPWeb varWeb)        {            try            {                var strMasterUrl = "/_catalogs/masterpage/myMasterPage.master";
                varWeb.AllowUnsafeUpdates = true;                varWeb.MasterUrl = strMasterUrl;                varWeb.CustomMasterUrl = strMasterUrl;                varWeb.Update();                varWeb.AllowUnsafeUpdates = false;            }            catch (Exception e)            {                throw new SPException("Error when trying to Set MasterPage. Error: " + e.Message);            }        }

Set draft security visibility to document library

2013-03-08T20:06:00.000+02:00

To set security that only approver and administrator see pending files

Set DraftVerrsionVisibility=”2” in Schema.xml

To learn more about DraftVersionvisibility please read this DraftVisibility Types

1- Using xml

<List xmlns:ows="Microsoft SharePoint" EnableContentTypes="TRUE" Title="Articles" Direction="$Resources:Direction;" Url="Lists/Articles" BaseType="1" xmlns="http://schemas.microsoft.com/sharepoint/" ModeratedList="TRUE" DraftVersionVisibility="2">

2- Programmatically

   private void applyApproverDraftVisibilityToAllLists(SPWeb oWeb)

        {            oWeb.AllowUnsafeUpdates = true;            SPListCollectionAdapter listAdapter = new SPListCollectionAdapter(oWeb.Lists);            var result = from list in listAdapter                         select list;            foreach (SPList list in result)            {                list.DraftVersionVisibility = DraftVisibilityType.Approver;            }            oWeb.AllowUnsafeUpdates = false;        }public class SPListCollectionAdapter : List<SPList>
    {        private readonly SPListCollection _listCol;        public SPListCollectionAdapter(SPListCollection listCol)        {            _listCol = listCol;            Refresh();        }        private void Refresh()        {            Clear();            foreach (SPList item in _listCol)            {                Add(item);            }        }    }

Hide approve state column from all lists

2013-03-08T19:57:00.003+02:00

[Code]

private void hideApproveStateColumn(SPWeb oWeb)
        {            oWeb.AllowUnsafeUpdates = true;
            SPListCollectionAdapter listAdapter = new SPListCollectionAdapter(oWeb.Lists);
            var result = from list in listAdapter                         select list;
            foreach (SPList list in result)            {                if (list.EnableModeration == true)                {                    string ApprovalStatusColumnName = "_ModerationStatus";                    SPView defaultView = list.DefaultView;                    if (defaultView.ViewFields.SchemaXml.Contains(ApprovalStatusColumnName))                    {                        defaultView.ViewFields.Delete(ApprovalStatusColumnName);                        defaultView.Update();                    }                }            }            oWeb.AllowUnsafeUpdates = false;        }

create view to List programaticallly

2013-03-08T19:56:00.001+02:00

[Code]

private void CreateView(SPWeb oWeb)
        {
            SPSecurity.RunWithElevatedPrivileges(delegate()            {                string strViewName = "myView";                bool bAlreadyExists;
                SPList oList = oWeb.Lists["Pages"];                SPViewCollection oViewCollection = oList.Views;
                var newWeb = GetRootWeb(oWeb);
    addContentTypeToList(oList);
                StringCollection viewFields = AddFieldsToView();
                bAlreadyExists = CheckViewExist(oViewCollection);
                if (bAlreadyExists) return;                  oViewCollection.Add(strViewName, viewFields, Query, 10, true, false);                oWeb.Update();            });        }
        private string Query        {            get            {                string query;                query = string.Format(@" <Where>   <Eq>                                            <FieldRef Name='ContentType' />                                            <Value Type='Computed'>{0}</Value>                                        </Eq>   </Where>     <OrderBy>     <FieldRef Name='Created' Ascending='FALSE' />                       </OrderBy>", mycontentType);
                return query;            }        }
        private static StringCollection AddFieldsToView()        {            StringCollection viewFields= new System.Collections.Specialized.StringCollection();
            try            {                viewFields.Add("field1");                viewFields.Add("field2");                viewFields.Add("field3");                viewFields.Add("field4");            }            catch (Exception e)            {                //write code when exception happen            }            return viewFields;        }

   private static SPWeb GetRootWeb(SPWeb oWeb)        {            SPWeb newWeb = oWeb;            while (!newWeb.IsRootWeb)            {                newWeb = newWeb.ParentWeb;            }            return newWeb;        }

private void addContentTypeToList(SPList oList)        {            if (oList.ContentTypes[myCTName] == null)            {                oList.ContentTypes.Add(myCT);                oList.Update();            }        }
        private static bool CheckViewExist(SPViewCollection oViewCollection)        {            bool bAlreadyExists=false;
            foreach (SPView vItem in oViewCollection)            {                if (vItem.Title == "myView")                {                    bAlreadyExists = true;                    break;                }
            }            return bAlreadyExists;        }

Create DiscussionBoard Programatically

2013-03-08T19:26:00.000+02:00

[Code]

private void CreateDiscussionBoardListToSite(SPWeb oWeb,string listNameEn,string listDescEn,string listNameAr,string listDescAr)        {            SPList list = oWeb.Lists.TryGetList(listNameEn);            if (list!=null) return;
            oWeb.AllowUnsafeUpdates = true;            Guid listId = oWeb.Lists.Add(listNameEn, listDescEn, SPListTemplateType.DiscussionBoard);            SPList createdList = oWeb.Lists[listId];            createdList.OnQuickLaunch = true;
            createdList.TitleResource.SetValueForUICulture(new CultureInfo(1033), listNameEn);            createdList.TitleResource.SetValueForUICulture(new CultureInfo(1025), listNameAr);            createdList.TitleResource.Update();
            createdList.DescriptionResource.SetValueForUICulture(new CultureInfo(1033), listDescEn);            createdList.DescriptionResource.SetValueForUICulture(new CultureInfo(1025), listDescAr);            createdList.DescriptionResource.Update();

            createdList.Update();        }

create default home page and add webparts on sitedefinition

2013-03-08T19:23:00.001+02:00

11- Create home.aspx page bye adding textfile and change extension .aspx

22- Open home.aspx and write magic code :

<%@ Page Inherits="Microsoft.SharePoint.Publishing.TemplateRedirectionPage,Microsoft.SharePoint.Publishing,Version=14.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %> <%@ Reference VirtualPath="~TemplatePageUrl" %> <%@ Reference VirtualPath="~masterurl/default.master" %>

33- Open onet.xml and add these lines

<Modules>    <Module Name="DefaultBlank" Url="Pages" Path="">
      <File Url="Home.aspx" Path="Home.aspx" Type="GhostableInLibrary">
        <Property Name="Title" Value="Home" />
        <Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/HomeLayout.aspx, Home Default Layout" />
        <Property Name="ContentType" Value="myPagesCT" />
        <AllUsersWebPart WebPartZoneID="myWebpart" WebPartOrder="1">
          <![CDATA[

<!—your webpart code à]]>        </AllUsersWebPart>
</File></Module></Modules>