Sunday, March 24, 2013

Create custom page layout in SharePoint 2013

In this post we will discuss about custom page layout in SharePoint 2013. Also you can see how to Create Page Layout using SharePoint Designer 2010, and also you can check how to Change page layout programatically in publishing site.

To create a page layout follow below steps:

Step-1:
Open the SharePoint site, Then navigate to Site Settings and under Look and Feel section click on Design Manager.

Step-2:
Then from the Layouts page, Click on the Edit Page Layouts and then from the right hand side click on Create a page layout.

Step-3:
The above step will open the Create page layout page. In this page give the page layout name, select the master page which it should associate and then select the content type and then click on OK.

Step-4:
Now the page layout will be available when you will try to edit the page.

Remember in SharePoint 2013, the page layout have 2 files now, one .aspx file and .html file.

You can also check Cross site publishing in SharePoint 2013, image rrenditions in SharePoint 2013 and What's new for mobile devices in SharePoint 2013.


Saturday, March 23, 2013

Create visual webpart in SharePoint 2013

In this post we will discuss how to create a visual webpart in SharePoint 2013 using Visual Studio 2012. Also you can check reindex feature in list and document library in SharePoint 2013, What's new in developer dashboard in SharePoint 2013 and New webparts in SharePoint 2013.

In SharePoint 2013, both web user control and the webpart class are merged to one template file, not like SharePoint 2010.

To create visual webpart follow below steps:

Step-1:
Open Visual Studio 2012, From the left side select Office/SharePoint and then from the right hand side select SharePoint 2013 Visual Web Part.

Step-2:
In SharePoint 2013 you can deploy visual webpart as a sandboxed solution apart from farm solution. So in the Next screen select Deploy as a farm solution and click on Ok. Also you can give the site URL for debugging.

Step-3:
Then write the code in the code behind file as in SharePoint 2010.

Step-4:
After finish coding you can debug or deploy the webpart.


Wednesday, March 20, 2013

Hover panel in SharePoint 2013 search results

In this post we will discuss about the new hover panel introduced in SharePoint 2013 search. You can also check out some new features like CAML designer for SharePoint 2013, New in developer dashboard in SharePoint 2013 and OAuth in SharePoint 2013.

There are huge improvements towards SharePoint 2013 search interface compared to SharePoint 2010, So that it will be more familiar to users of popular search engines like google.

SharePoint 2013 introduced a new thing known as hover panel. This will be visible when user hover a search result item. This is basically a panel which shows some more information about the search result.

It provides information like:

- Search popularity and view counts from the analytic component.

- A preview for Word, Excel and PowerPoint documents as long as we have Office Web Apps available or some other rich preview such as an image or video.

- Additional actions i.e. Follow, Edit or View this content etc.


Saturday, March 16, 2013

New for visual webpart for SharePoint 2013 and Visual Studio 2012

In this post we will see a new improvements in visual webpart for SharePoint 2013 and Visual Studio 2012.

Also you can check Change master page in SharePoint 2013, What is new in developer dashboard in SharePoint 2013 and OAuth in SharePoint 2013.

In visual studio 2010, visual webparts can be created towards only farm solution. But in SharePoint 2013, you can create visual webparts as sandboxed projects as well as farm solution project.

When you will create the project it will ask you wether you want to create as a farm solution or as a sandboxed solution.

When developing sandboxed solutions, Visual Studio IntelliSense now only displays APIs that are available in the sandboxed solutions.

In SharePoint 2013 visual webpart now the User Control and WebPart Classes are merged to Create one template. There will  be no two file like in visual studio 2010 template where we had separate ascx and webpart file.


Twitter Delicious Facebook Digg Favorites More