Friday, November 30, 2012

Save site as template in SharePoint 2013

In this article we will discuss how to save site as a template in SharePoint 2013. You can also check out my previous articles on SharePoint 2013 boundaries and limits, New web parts in SharePoint 2013.

Open the site and go to Site settings. Then go to Site Actions.

From the Site Actions sections select Save site as template.

This will open the Save site as template page.

There give the file name, Template name, Template description. If you want to include the content of the list then check the check box "Include Content".

Then click on OK, then it will show the Operation Completed Successfully message.

Now check the solution gallery the template will be available there.

Some Points to remember here:
- In SharePoint 2013, no more .stp file, the template will be saved in extension as .wsp.

- Not possible to save site as template for publishing site or publishing feature enabled sites.

Wednesday, November 28, 2012

What's new in Developer dashboard in SharePoint 2013?

In this blog we will discuss about what is new in developer dashboard in SharePoint 2013. You can read an article on Developer dashboard in SharePoint 2010. Also you can read my last articles on What are the new web parts in SharePoint 2013, What's new in workflow in SharePoint 2013? and Browsers supported by SharePoint 2013.

Here are few things new in Developer dashboard in SharePoint 2013:
- As we know ULS logs are very much important while debugging, Developer dashboard comes with a dedicated tab to see ULS logs for a particular request.

- Ondemand option is deprecated in SharePoint 2013, But you can use PowerShell to enable or disable Developer dashboard.

- Developer dashboard now opens in a separate window.

- Provides detailed information using chat view.

- Like in SharePoint 2010 developer dashboard is off or disable by default.

Wednesday, November 7, 2012

OAuth in SharePoint 2013

In this blog we will discuss about What is OAuth in SharePoint 2013. You can also check some new features of SharePoint 2013 as well as hardware and software requirements in SharePoint 2013.

When a user signs in to SharePoint 2013, the user's token is validated and then used to sign in to SharePoint. The user's token is a security token that is issued by an identity provider.In the case of app authentication, the authentication process verifies a claim that is made by a subject that it should be allowed to act on behalf of a given principal. Apps can be authenticated in several different ways. When a call is made to an app web, if the call is an OAuth call, SharePoint 2013 uses the Windows Azure Access Control Service (ACS) as the app identity provider.

OAuth is an open protocol for authorization. OAuth enables secure authorization from desktop and web applications in a simple and standard way. OAuth enables users to approve an application to act on their behalf without sharing their user name and password. It allows users to use resources like contact list, documents, photos, videos etc that are stored on one site with another site, without users having to provide their credentials.

OAuth enables users to authorize the service provider to provide tokens instead of credentials  to their data that is hosted by a given service provider. Each token grants access to a specific site for specific resources and for a defined duration.

OAuth is required in following cases:
- To authorize requests by an app for SharePoint to access SharePoint resources on behalf of a  user.
- To authenticate apps in the Office Store, an app catalog, or a developer tenant.

Follow for more reference:

Different ways to access SharePoint 2013 list data

In this blog we will discuss about different ways to access SharePoint list data using client APIs. In my previous posts we have discussed about API references in SharePoint 2013, Create list using SharePoint 2013 client object model and New web parts in SharePoint 2013.

Inside an SharePoint App, you can use different client APIs for business logic. Below are some APIs:

- .NET Framework client object model: This is available in a redistributable package from SharePoint Client Components. If you prefer LINQ syntax, you can use it with this library.

- Silverlight client object model: This is also available in the same redistributable package and you can also use LINQ syntax with it.

- JavaScript client object model: This is a library in a .js file that includes all the same functionality as the managed code object models.

- REST endpoints: SharePoint 2013 provides REST/OData endpoints that can be accessed from any web client, including non-Microsoft clients and servers. If you prefer to use LINQ syntax, you can do so with this same web service from any .NET Framework platform.

- Mobile client object model: This is available for use on Windows Phone. devices. The assemblies are available in %ProgramFiles%\Common Files\Microsoft Shared\web server extensions \15\TEMPLATE\LAYOUTS\ClientBin and must be included in the .xap file of the mobile app.

Sunday, November 4, 2012

SharePoint 2013 workflow video

This video shows SharePoint 2013 designer workflow. It also explain how to create a workflow in SharePoint 2013 as well as explain about Task process designer. This video is presented by Laura Rogers a Microsoft MVP. Also check what is new in workflow in SharePoint 2013.

The task process designer is really very good in SharePoint 2013 workflow.

Friday, November 2, 2012

SharePoint 2013 user interfaces video

This is a video that clearly explains about SharePoint 2013 user interface. This video is presented by a Microsoft certified SharePoint trainner Asif Rehemani who himselft a SharePoint videos web site

This video explains topics like how to create team site in SharePoint 2013, explains about the top navigation, also give some inforamtion about site mailbox, Quick Links, Site Settings, Document library etc.

Twitter Delicious Facebook Digg Favorites More