Wednesday, October 30, 2013

Change local debugging URL in visual studio 2012 for SharePoint 2013

In this post we will discuss how we can change the local debugging URL in visual studio 2012 for SharePoint 2013. Also you can check my previous posts on:

- Create Site in SharePoint Online

- Get website title using SharePoint 2013 client object model

- Create workflow using SharePoint designer 2013 in SharePoint 2013


If you are developing any SharePoint 2013 solution using Visual Studio 2012, then it will ask you to enter the local debugging URL in SharePoint Customization Wizard.

If you want to change that after creation time, then follow below steps:

- Open Properties window, Either you can go View -> Properties Window or you can Right click on the Project and Select Properties Window as shown in the fig below:


- Then in the Properties window, Change Site URL Property to the new URL what ever you want to give.

Next time when you will debug or deploy, the New URL will be hit.


Different authentication types supported in SharePoint 2013

In this post we will discuss about different authentication types supported in SharePoint 2013. Also you can check my previous posts on:

- SharePoint 2013 deployment Scenarious

- Create an Application Page in SharePoint 2013 using Visual Studio 2012

- What's new for mobile devices in SharePoint 2013 ?
SharePoint 2013 supports 4 types of authentication:

- Anonymous authentication
- Windows authentication
- Forms-based authentication
- SAML token-based authentication

Anonymous authentication:
In Anonymous authentication type users can access SharePoint content without validating their credentials. Anonymous authentication is disabled by default.

You can use Anonymous authentication if sharepoint content does not require security and is available for all users like any public Internet website.

Windows authentication:
Here in windows authentication, a Windows domain environment uses to validate the credentials like AD DS. This is used by both claims-based authentication and classic mode and it also includes:
- NTLM
- NTLM
- Digest
- Basic

Forms-based authentication:
Forms-based authentication is a claims-based identity management system that is based on ASP.NET membership and role provider authentication. Forms-based authentication can be used against credentials that are stored in an authentication provider like:
- AD DS
- SQL Server database
- Lightweight Directory Access Protocol (LDAP) data store such as Novell eDirectory, Novell Directory Services (NDS), or Sun ONE

Forms-based authentication validates users based on credentials that users type in a logon form. Unauthenticated requests are redirected to a logon page, where a user must provide valid credentials and submit the form. The system issues a cookie for authenticated requests that contains a key for reestablishing the identity for subsequent requests.

SAML token-based authentication:
SAML token-based authentication in SharePoint 2013 uses the SAML 1.1 protocol and the WS-Federation Passive Requestor Profile (WS-F PRP). If you use Active Directory Federation Services (AD FS) 2.0, you have a SAML token-based authentication environment.

The authentication providers for SAML token-based authentication may be:
- Windows Server 2003 Active Directory and AD DS in Windows Server 2008
- All editions of SQL Server 2005 and SQL Server 2008
- Custom attribute stores

you can get some more information here.


Tuesday, October 29, 2013

Create an Application Page in SharePoint 2013 using Visual Studio 2012

In this post we will discuss how to create an application page in SharePoint 2010 using Visual Studio 2012. If you want to check how to create an application page using visual studio 2010 in sharepoint 2010, then you can see this article.

Also you can check out my previous posts on:

- Office Developer Tools for Visual Studio 2012 for SharePoint 2013

- What's new in Developer dashboard in SharePoint 2013?

- Friendly URL in SharePoint 2013

You can get more information on application pages as well as you can check what is the difference between site pages and application pages.

First open Visual Studio 2012, then from the left side select Office/SharePoint -> SharePoint Solutions and there select SharePoint 2013 - Empty Project as shown in the fig below:


Then in the SharePoint Customization wizard, give the local site for debugging as well as chose Deploy as a farm solution. There are certain limitations in Sandboxed Solution.

- Then right click on the project -> Add New Item and then from the Add New Item dialog box, chose Application Pages (Farm Solutions only) template.

- Then you can put some controls to the application page, as well as you can write some code for that.

- Now Build and Deploy the project, If it is deployed successfully, then we can browse the application page. In SharePoint 2013, application pages deployed to C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS folder location.

- We can browse the page like below:
http://SiteURL/_layouts/Project-Name/Name-of-Application-Page.aspx


Monday, October 28, 2013

Hide ribbon in InfoPath form in SharePoint 2013

Here we will see how we can hide ribbon in infopath 2013 in sharepoint 2013. Also you can check out my previous posts on:
- Zip code validation in InfoPath 2010

- SharePoint Server 2013 databases

- Default permission levels in SharePoint 2013

Open infopath 2013 form, Go to File and then click on Advanced form options as shown in the fig below:



This will open the Form Options dialogbox. In the Form Options dialog box, see the Web Browser category. There uncheck "Show InfoPath command in Ribbon or toolbar". Then click on OK as shown in the figure below this will hide the Ribbon in the infopath form.


Sunday, October 27, 2013

Share with everyone new feature in SharePoint 2013

In this post we will discuss about "Share with everyone" feature in SharePoint 2013. Also you can check out my previous post:

- Image Rendition feature in SharePoint 2013

- Advantages of Apps in SharePoint 2013

- Create workflow using SharePoint designer 2013 in SharePoint 2013

Share with everyone is a new feature like microblog sites like twitter. You can start a conversation with people by posting to the public newsfeed. People who are following you can see the post. And any one who see the post can reply to the post also.

Apart from text you can also post links, videos, documents, pictures etc.


To start with:

Click on the Newsfeed at the top of the page, Then click on Share with everyone textbox and type the text and then click on Post.

If you want to reply then you can click on the reply button and then reply to the conversion. You can not reply to other replies.

But there are also some conversations which are "locked" and do not allow additional replies.


SharePoint Server 2013 databases

In this post we will discuss about SharePoint server 2013 databases in SharePoint 2013 deployments. In my last post we discussed about various databases which are presented in both SharePoint Foundation 2013 and SharePoint Server 2013 deployments.

Also you can check out my previous posts on:

- Change default error and successful message in infopath 2013

- HTML Field Security option in SharePoint 2013

- Difference between Apps and Solutions in SharePoint 2013

- SharePoint User Profile service application databases:

The User Profile service has three databases that support SharePoint Server 2013.
1- Profile: It stores and manages users and associated information.

Default Database Name: User Profile Service Application_ProfileDB_<GUID>

2- Synchronization: This stores configuration and staging data for use when profile data is being synchronized with directory services such as Active Directory.

Default Database Name: User Profile Service Application_SyncDB_<GUID>

3- Social Tagging: The Social Tagging database stores social tags and notes created by users, alongside their respective URLs.

Default Database Name: User Profile Service Application_SocialDB_<GUID>


- Word Automation Services service application database:

This database stores information about pending and completed document conversions and updates.

Default Database Name: WordAutomationServices_<GUID>

- Managed Metadata Service service application database:

The Managed Metadata service application database stores managed metadata and syndicated content types.

Default Database Name: Managed Metadata Service Application_Metadata_<GUID>

- SharePoint Translation Services service application database:

The Machine Translation Services stores information about pending and completed batch document translations with file extensions that are enabled.

Default Database Name: SharePoint Translation Services_<GUID>

- Project Server service application database:

Project Server database contains data about All Project and Portfolio Management (PPM) data, Time tracking and Timesheet data and Aggregated SharePoint project site data.

Default Database Name: ProjectWebApp

- PerformancePoint Services service application database

The PerformancePoint Services database stores temporary objects and persisted user comments and settings.

Default Database Name: PerformancePoint Service _<GUID>

- State Service service application database

It stores temporary state information for InfoPath Forms Services, Exchange Server, the chart Web Part, and Visio Services.

Default Database Name: SessionStateService_<GUID>

More information you can get in technet article.


Friday, October 25, 2013

SharePoint 2013 service application databases

In this post we will discuss about various service application databases available in SharePoint 2013.

Also you can check out my previous posts on:

- Configure Following settings in SharePoint 2013

- Timeline web part in SharePoint 2013

- App parts in SharePoint 2013

The below are the databases which are presented both in SharePoint Foundation 2013 and SharePoint Server 2013 deployments.
- App Management database

App Management database stores the app licenses and permissions that are downloaded from the SharePoint Store or App Catalog, and is used by App Management Service application.

Default Database Name: AppManagement

- Business Data Connectivity database

The Business Data Connectivity service application database stores external content types and related objects.

Default Database Name: Bdc_Service_DB_<GUID>

- Search service application databases

The Search service application has four databases that support SharePoint 2013.

1- Search Administration: The Search Administration database hosts the Search service application configuration and access control list (ACL) for the crawl component.

Default Database Name: Search_Service_Application_DB_<GUID>

2- Analytics Reporting: The Analytics Reporting database stores the results for usage analysis reports and extracts information from the Link database when needed.

Default Database Name: Search_Service_Application_AnalyticsReportingStoreDB_<GUID>

3- Crawl: The Crawl database stores the state of the crawled data and the crawl history.

Default Database Name: Search_Service_Application_CrawlStoreDB_<GUID>

4- Link: The Link database stores the information that is extracted by the content processing component and the click through information.

Default Database Name: Search_Service_Application_LinkStoreDB_<GUID>

- Secure Store Service database

The Secure Store Service application database stores and maps credentials, such as account names and passwords.

Default Database Name: Secure_Store_Service_DB_<GUID>

- Usage and Health Data Collection database

Usage and Health Data Collection database stores health monitoring and usage data temporarily, and can be used for reporting and diagnostics and is used by Usage and Health Data Collection service application.

Default Database Name: SharePoint_Logging

- Subscription Settings database

It stores features and settings for hosted customers.

Default Database Name: SettingsServiceDB

There are other databases which are specific to SharePoint server 2013, we will discuss in other article.


Wednesday, October 23, 2013

Sharepoint 2013 object model code sample download

Here is a good link to download code samples for SharePoint 2013 object model.

The code sample includes:
- demonstrate apps for SharePoint
- BCS
- user experience design
- metadata management
- workflows
- mobile application development
- REST
- other areas of SharePoint development.
The code sample are in C#.Net in Visual Studio 2012.

You can download SharePoint 2013 object model from this link.

Also you can check out some articles on:

- Follow or UnFollow people by using SharePoint 2013 client object model

- Update website properties in SharePoint 2013 client object model

- Create SharePoint website using SharePoint 2013 client object model


Different database in SharePoint 2013

In this post we will discuss about different database in SharePoint 2013 deployments. Also you can check out some articles on:

- Continuous Crawl in SharePoint 2013 search

- Steps to create a task list in SharePoint 2013

- Follow or UnFollow people by using SharePoint 2013 client object model

There are 3 types of databases installed when you deploy SharePoint 2013 and they are: Configuration database, Central Administration Content and Content database.

Configuration database:

The configuration database contains data about:

- SharePoint databases

- Internet Information Services (IIS) web sites

- Web applications

- Trusted solutions

- Web Part packages

- Site templates

- Web applications

Also it contains information about default quota settings and blocked file types etc.

The default database name when it is installed with the SharePoint Products Configuration Wizard is: SharePoint_Config


Central Administration content database:

Central Administration content database stores all configuration data for the Central Administration site collection.

The default database name prefix when it is installed by using the SharePoint Products Configuration Wizard is SharePoint_Admin_Content.

Content databases:

Content databases store all content for a site collection. This includes site documents or files in document libraries, list data, Web Part properties, audit logs, and sandboxed solutions, in addition to user names and rights.

All of the files that are stored for a specific site collection are located in one content database on only one server. A content database can be associated with more than one site collection.

The default database name when installed by using the SharePoint Products Configuration Wizard is WSS_Content. Followed from technet article.


Friday, October 18, 2013

Sharepoint Designer cannot display this item error after migrating from SharePoint 2010 to SharePoint 2013

Here we will discuss how to resolve SharePoint 2013 designer error which comes once you migrate from SharePoint 2010 to SharePoint 2013.

The error message ususally comes as: Sharepoint Designer cannot display this item. This error comes if you try to open and modify a workflow.

This error usually comes if you have SharePoint designer 2010 before installing SharePoint designer 2013.

So the solution (not sure correct or not but works for me) is to delete the cache for SharePoint designer. So open the below directory and delete the contents.

C:\Users\yourname\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache

After this hope the error will not come to you.

You can also check out my previous posts on:

- Create update Delete list item using SharePoint 2013 object model

- Hosting options in SharePoint 2013

- Image Rendition feature in SharePoint 2013


Default permission levels in SharePoint 2013

Like in SharePoint 2010, SharePoint 2013 also provides some default permission levels. Also you can check out my previous posts on:

- Timeline web part in SharePoint 2013

- Create workflow using SharePoint designer 2013 in SharePoint 2013

- Populate profile properties in infopath in SharePoint 2010

SharePoint 2013 includes seven permission levels:

- View Only: It enables users to view application pages.

- Limited Access: It enables users to access shared resources and a specific asset. Limited Access cannot be edited or deleted.

- Read: It enables users to view pages and list items, and to download documents.

- Contribute: Contribute enables users to manage personal views, edit items and user information, delete versions in existing lists and document libraries, and add, remove, and update personal Web Parts.

- Edit: It enables users to manage lists.

- Design: Design permission level enables users to view, add, update, delete, approve, and customize items or pages in the website.

- Full Control: It enables users to have full control of the website.

Apart from this SharePoint 2013 also provides some permission levels to templates other than team site template. These are below:

- Restricted Read: This permission level is only for Publishing sites only. It enables View pages and documents.

- Approve: This permission level is only for Publishing sites only. It enables Edit and approve pages, list items, and documents.

- Manage Hierarchy: This permission level is only for Publishing sites only. Create sites; edit pages, list items, and documents, and change site permissions.


Thursday, October 17, 2013

Office Developer Tools for Visual Studio 2012 for SharePoint 2013

In this post we will discuss about how to install office developer tools for visual studio 2012. Also you can check my previous posts on:

- Timeline web part in SharePoint 2013

- Content by Search (CBS) Web Part in SharePoint 2013

- Create update Delete list item using SharePoint 2013 object model

By default in Visual Studio 2012, the templates required for SharePoint 2013 will not come like template to develop Apps in SharePoint 2013, Apps for Office 2013, SharePoint-2013 Empty Project etc.

So for this we need to install office developer tools for Visual Studio 2012. You can download from this link and then install.

If error comes then try to install multiple times (this worked for me), once installation completes then templates will come like below:




Monday, October 14, 2013

Create new task in task list in SharePoint 2013

In this post we will discuss how to create a new task in SharePoint 2013 task list. Also you can check my previous posts on:

- Add user to SharePoint security group using SharePoint client object model

- Create SharePoint website using SharePoint 2013 client object model

- Get current user email by using SharePoint 2013 object model

To create a new task to a task list open the task list and click on new task link and this will open the New task page.

In this page:
- Enter the Task Name
- Start Date
- Due Date
- Assigned To
- % Complete
- Description
- Predesessors
- Priority
-Task Status etc.
Fill all the details above and click on Save.

A new task will be get created.


Steps to create a task list in SharePoint 2013

In this post we will discuss how to create a task list in SharePoint 2013. Also you can check some SharePoint 2013 articles like:
- Timeline web part in SharePoint 2013

- Continuous Crawl in SharePoint 2013 search

- Build hyperlink inside email in SharePoint 2010 designer workflow

Task list is very useful for the collaboration feature.

First Open your SharePoint 2013 site. If you are new to SharePoint 2013, then you can see this article on how to create a site collection in SharePoint 2013.

Then from the Quick Launch bar, Click on Site Contents.

This will open the Site Contents page which usually contains the lists, libraries and other apps.

In this page click on add an app icon and this will open the apps page.

There select the Tasks app as shown in the figure below:


This will ask you to put a name for the Tasks and click on Create.

It will now create the Tasks list.


Tuesday, October 8, 2013

Timeline web part in SharePoint 2013

In this post we will discuss how to add timeline web part into a SharePoint page in SharePoint 2013. Also you can check:
- Create custom page layout in SharePoint 2013

- Get UserProfile using SharePoint 2013 object model

- SharePoint 2013 Workflow Installation and Configuration

Timeline webpart is a new web part added into SharePoint 2013. The Timeline web part provides the timeline without the Summary or Quick Edit links. The Timeline web part provides the ability to move the layout of the tasks.

To add a timeline web pat to a page follow below steps:

- Edit the SharePoint page and then from the Ribbon click on Insert Tab and from there click on Web Part icon.

- This will open the webpart categories page, where it will show list of webparts. From there select the "Content Rollup" category. In this category select "Timeline" web part and then click on Add as shown in the fig below.


- This will add the timeline web part to the page successfully.

- Then we need to give a datasource to the timeline web part. The data source can come from other site collections also. This data source url is nothing but a task list url.

- To give the datasource url, edit the timeline web part and then in the Data Source section, give the data source url in the Select the data source to connect to the timeline. Here we need to select the task list url.

- It will look like below:


Friday, October 4, 2013

Different search syntax supported by SharePoint 2013

In this post we will discuss about various search syntax supported by SharePoint 2013 for building search queries. Also you can check out my previous posts on:

- Installing or Uninstalling Features in SharePoint 2013

- Retrieve all SharePoint list in SharePoint 2013 client object model

- Create visual webpart in SharePoint 2013

SharePoint 2013 supports 2 types of languages syntax to build search queries:

- Keyword Query Language (KQL)

- FAST Query Language (FQL)

Keyword Query Language (KQL):
- This is the default language to build search queries.

- By using KQL, you specify the search terms or property restrictions that are passed
to the SharePoint search service. For more information you can check here.

- Also you can check some enhancements in Keyword Query Language.

FAST Query Language (FQL):

- FQL is a structured query language that supports advanced query operators.

- You can use FQL when you want to create complex queries that you want to pass programmatically to the SharePoint search service.

- FQL isn't intended to be exposed to end users, and is disabled by default.

For more information you can check here.


Twitter Delicious Facebook Digg Favorites More