What is NOT there in SharePoint 2013?

In this article we will discuss some of the features which are not there in SharePoint 2013. You can check also check SharePoint 2013 Apps and browsers supported by SharePoint 2013.

1. SharePoint 2013 also removed one feature in SharePoint 2010 designer. Previously SharePoint 2010 designer has Design, Split and Code view for editing Aspx/Html pages. But SharePoint 2013 removed Design and Split view, now only Code view is presented in SharePoint 2013. This changed feature is

Difference between SharePoint 2013 and SharePoint 2010

As we know Microsoft has released the next version of SharePoint 2010 which is called as SharePoint 2013(preview), here we will discuss about some new features of SharePoint and some features missed from SharePoint 2010.

1- In SharePoint 2013 a very new thing introduced known as Cloud App Model. You can check this article for more on SharePoint 2013 apps.

Social networking feature in SharePoint 2013

In this article we will discuss something about social networking features improved in SharePoint 2013. In this article we will discuss some Twitter terms in SharePoint 2013 like follow, @, #tag etc.

A user can follow  People, Documents, Sites and Tags. Following is a good feature introduced in SharePoint 2013 to stay connected with people and content the user likes.

1. Follow or UnFollow:
A user can follow people, content etc. If you follow a people, then  the posts and activities of the followed people show up in the user's newsfeed. You can also work with follow using client object model or server object model. You can check this article http://msdn.microsoft.com/en-us/library/jj163133(v=office.15).aspx

User also can follow contents. When users following documents, sites, or tags, they get status updates about the followed items in their newsfeed. The features related to following content can be seen on the Newsfeed and the Following content pages on My Site. You can also work with follow or unfollow using SharePoint client object model or server object model. You can follow the msdn site for more. http://msdn.microsoft.com/en-us/library/jj163217(v=office.15).aspx

If you do not want any updates, you can UnFollow them.

2. @ and #tag:
Like in Twitter we use @ and #, Here in SharePoint 2013 we can use @ and # tag for content as well as people. If user enters a tag, SharePoint helpfully provides some recommendations for the user to select from. If a user is identified using the @ tag, they will receive a Mention in their Newsfeed, as well as an email the way it works in Twitter.

Apps in SharePoint 2013

As we know SharePoint 2013 has some improved features, in this article we will describe What are Apps in SharePoint 2013? You can also check hardware and software requirements in SharePoint 2013.

Also you can check out:

- Steps to create App Catalog site in SharePoint 2013

- How to get userprofile properties in SharePoint 2013 object model?

- How to disable mobile page redirection for SharePoint 2013?

An app for SharePoint is a web application that is registered with SharePoint using an app manifest. An app manifest is an XML file that declares the basic properties of the app along with where the app will run and what to do when the app is started.

Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. Apps integrate the best of the web and SharePoint; they are targeted, lightweight, and easy-to-use, and do a great job at solving a user need. Users discover and download apps from the SharePoint Store or from their organization's private App Catalog and install them on their SharePoint sites.

 You can use any language, such as HTML, JavaScript, PHP, or .NET, and you can also use Microsoft Visual Studio 2012 also.

Through apps in SharePoint 2013 we can read documents, add posts, can do searches, can connect with people, and so on. We can also connect with and from Search, workflow, social networking, taxonomy, user profiles, BCS, and more from SharePoint 2013 app using SharePoint APIs. We can use 1. REST and JavaScript APIs and 2. Managed APIs (.Net)

SharePoint 2013 apps can be hosted  in 3 different places like:

1- SharePoint 2013 apps can be hosted in SharePoint itself and the code is HTML and JavaScript. When you deploy a SharePoint-hosted app, SharePoint creates a new website called the app web. SharePoint 2010 web store pages, lists, and libraries.

2- Host in the cloud:
SharePoint automatically deploys the app into Windows Azure Web Sites and SQL Azure, and these apps run in the cloud.

3- Can be hosted in mix components in SharePoint and cloud:
SharePoint components run in SharePoint, and components hosted in the cloud run in the cloud.

SharePoint 2013 interview questions and answers

Here are some SharePoint interview questions and answers mentioned inline. Also you can check some SharePoint 2010 interview questions and answers as well as you can check some Asp.Net interview questions and answers here also.

Some SharePoint 2013 interview questions and answers:

What's new in SharePoint 2013 compared to SharePoint 2010?

SharePoint 2013 supports which version of .Net framework?

Difference between SharePoint 2013 and SharePoint 2013 preview?

What are the new features in SharePoint 2013 compared to SharePoint 2013 foundation server?

What are the SharePoint 2013 installation requirement?

What's new for developers in SharePoint 2013?

What's new for IT Pros in SharePoint 2013?

What are Apps in SharePoint 2013?

What are the different browsers supported in SharePoint 2013?

How SharePoint 2013 search works?

What are the new SharePoint 2013 search webparts introduced?

What are the new workflows introduced in SharePoint 2013?

Can I reuse a SharePoint 2010 workflow in SharePoint 2013 Site?

What are the new web parts introduced in SharePoint 2013?

Does SharePoint 2013 supports Passport authentication?

What are the new master pages and page layouts introduced in SharePoint 2013?

Does Sandboxed solutions exists in SharePoint 2013?

Can I open a SharePoint 2013 site using SharePoint 2010 designer?

Can I reuse a SharePoint 2010 designer workflows in SharePoint 2013 site?

What is Windows Azure Workflow in SharePoint 2013?

What are the new improvements in Visual Studio 2012 for SharePoint 2013?

How SharePoint 2013 authentication works?

What are improvements in Social features in SharePoint 2013?

How to migrate from SharePoint 2010 to SharePoint 2013?

Browsers supported in SharePoint 2013

In this article we will discuss about the browsers supported by SharePoint 2013. Also you can check the hardware and software requirements for SharePoint 2013. Also you can check out SharePoint 2013 download links here.

Here we will discuss the browser and version supported by SharePoint 2013 and also some browsers SharePoint 2013 supported with some limitations.

Internet explorer 9:
SharePoint 2013 supports Internet explorer 9 32-bit versions as well as it supports 64-bit versions with some limitations.

Internet explorer 8:
SharePoint 2013 supports Internet explorer 8 32-bit versions as well as it supports 64-bit versions with some limitations.

Google Chrome (latest release versions):
SharePoint 2013 supports Google chrome 64-bit with limitations.

Mozilla Firefox (latest release versions):
SharePoint 2013 supports Mozilla Firefox 64-bit with limitations.

Apple Safari (latest release versions):
SharePoint 2013 supports Apple Safari  32-bit with limitations.

Browsers NOT supported by SharePoint 2013:
The following browsers are not supported by SharePoint 2013:
- Internet explorer 7

- Internet explorer 6

- Google Chrome 32 bit version

- Mozilla Firefox 32 bit version

- Apple Safari 64 bit version

Apart from the above details, browser supports also depends upon the Operation system. Below is the operating systems that support browsers.
Internet Explorer 8 and Internet Explorer 9:
- Windows Server 2008 R2

- Windows Server 2008

- Windows Server 2003

- Windows 7

- Windows Vista

- Windows XP

Google Chrome and Mozilla Firefox:

- Windows Server 2008 R2

- Windows Server 2008

- Windows Server 2003

- Windows 7

- Windows Vista

Apple Safari:
- Mac OSX (Snow Leopard and Lion)

- Windows 7

- Windows Vista

Federated Search in SharePoint 2010

In this article we will discuss about What is Federated Search in SharePoint 2010. Compared to MOSS 2007 SharePoint 2010 has improved Search. You can also check my last article on Fast Search in SharePoint 2010.

Also you can check out:

- Get icon for different file types in SharePoint 2010

- Hide search box in home page in SharePoint 2013

- Query Search with SharePoint 2013 server object model

Basically Federated Search displays search results for additional content that is not crawled by your search server. We can see the data from several sources without indexing them. This is very much helpful when data is stored in external sources, where we do not have control to crawl or index the data. Federated search passes queries to external search engines. And the results are returned from there to the index server.

For example we can show results from Bing or Google in our SharePoint 2010 site.

SharePoint provides an out of box webparts namely Federated results, which is used in SharePoint to show Federated results. In the properties we can defined the Location.

Here is an advantages of federated search in SharePoint according to MSDN.
- You require no additional capacity requirements for the content index, as content is not crawled by SharePoint Enterprise Search.

- You can take advantage of a repository’s existing search engine. For example, you can federate to an Internet search engine to search the Web.

- You can optimize the content repository's search engine for the repository's specific set of content, which might provide better search performance on the content set.

- You can access repositories that are secured against crawls, but which can be accessed by search queries.

You can see another article on SharePoint Search through Server Object Model 2010 and Fast Search in SharePoint 2010.

The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled

There is a chance that you will get error as "The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled" while working with SharePoint 2010 search. There are different reasons for this, but one of the popular reason is because by default sharepoint crawl a file size of 16MB. So it will always crawl 16 MB file, and after this limit reached, SharePoint show the error message "The file reached the maximum download limit. Check that the full text of the document can be meaningfully
crawled".

Site templates in SharePoint 2010

Site template is a very useful concepts in SharePoint 2010. Site template is nothing but a solution file with the extension of .wsp. Site templates stored in the solutions gallery of the top level site. Also check one article on  Detecting Memory Leaks in SharePoint 2010.

This is nothing but a package of everything like list, libraries, pages, sub sites etc. While packaging we can also save its contents like list items, documents, pages, custom pages, master pages and configurations. But some components like user permissions will not saved.

We can use the site template (solution file) in different site collections, but that server should contain the site definition files installed. Suppose you make the site template that internally derived from the Team site definition, then the other server should have Team site definition installed. Even if you have any content type used then those content types must be recreated in the other site collection.

The .wsp file is actually a cabinet file that contains a lots of xml files like elements.xml, Feature.xml, ONet.xml etc.

We can save the site as a template by using SharePoint designer 2010 or by using the browser.

By using SharePoint designer 2010:

First open the site by using SharePoint designer (Go to Start -> All Programs -> SharePoint -> Microsoft SharePoint Designer 2010). Then click on Open site and give the URL of the site.

Once the site is opened, from the site tab click on Save as Template as shown in the figure below:

This will open the  Save as Template page in the browser. For the rest of the steps we will discuss in the 2nd
option by using browser. Since afterwards both are same.

By using browser:

First open the site in the browser. Then go to Site Actions -> Site Settings.

This will open the site settings page, Navigate to the Site Actions section and click on Save site as template as shown in the figure below.

This will open the Save as Template page where you can give the File Name, Template Name, Template Description, and whether you want to include the content or not. Then click on OK as shown in the figure below:

When click on OK it will show a confirmation dialog box like below.

The solution is stored in the solution gallery. In my case the URL is

http://bsahoo3:2500/sites/TestSiteCollection/_catalogs/solutions/Forms/AllItems.aspx

From browser also you can navigate to the solution gallery.
Go to Site Actions -> Site Settings-> From the Galleries section you can click on Solutions. You will get the site template that we have created just now.

Programmatically get SharePoint Themes

In this article we will discuss how to get all sharepoint themes programmatically using SharePoint 2010 object model. Also you can check my last article on how to create custom theme in sharepoint 2010. Also you can check one more article on how to programmatically apply theme to sharepoint 2010 site.

For this example I am writting the code in a visual web part. All the Themes of the site will be printed in a Label.

Full code:

<asp:Label ID="lblThemes" runat="server"></asp:Label>

using System;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Utilities;
using System.Collections.ObjectModel;
using System.Text;

namespace SharePointPOC.VisualWebPart1
{
    public partial class VisualWebPart1UserControl : UserControl
    {
        protected void Page_Load(object sender, EventArgs e)
        {
            GetAllTheme();
        }

void GetAllTheme()
        {
            StringBuilder sb = new StringBuilder();
            using (SPSite siteCollection = new SPSite("http://bsahoo3:2500/sites/TestSiteCollection/"))
            {
                using (SPWeb web = siteCollection.OpenWeb())
                {
                    ReadOnlyCollection themes = ThmxTheme.GetManagedThemes(siteCollection);
                    foreach (ThmxTheme theme in themes)
                    {
                        sb.Append("\n");
                        sb.Append(theme.Name);
                    }
                }
            }
            lblThemes.Text = sb.ToString();
        }
    }
}

Once you will deploy the code then you will able to see the list of all themes belongs to the site as shown in the figure below

File Not Found error in SharePoint 2010

In this post we will discuss how to resolve File not found error in SharePoint 2010.

Also you can check out:

- Programmatically get SharePoint Themes

- Bind dropdownlist from SharePoint list in InfoPath 2010

- Correlation ID in SharePoint 2010

I got the File Not Found error in SharePoint 2010.

Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: ed7664ef-5896-4df5-865b-9feed32468ab

Actually I deployed a visual web part that I made using Visual Studio 2010. When I deploy the web part and try to add in the page I got the above error.

Reason:
There can be any reason for this like:

- As we know SharePoint 2010 supports .Net framework version 3.5, If we have selected the .Net framework version to 4.0 then we might got the issue.
- Another reason might be the Target framework. There are 3 target framework version like: x64, x86 and Any CPU. As SharePoint 2010 supports x64 only, so If you have selected target framework to x86 then the error might appear. The safiest approach is to choose target framework to Any CPU.

- Last reason, the way I solved the issue is quite different which is not related to any .Net framework. My visual web part contains some code like:

using (SPSite siteCollection = new SPSite("http://bsahoo3:2500/sites/TestSiteCollection/"))

Here I have given one site URL but I am deploying and trying to add the web part in a different URL. Once I changed the URL I did not got that issue.

Detecting Memory Leaks in SharePoint 2010

In this article we will discuss how we can detect memory leaks while working SharePoint 2010 object model. You can also check an article on SharePoint 2010 best practices. You can also check an article on SharePoint 2010 designer best practices and also you can check Causes of Performance issues in SharePoint 2010.

Memory leaks are very much in SharePoint. If we will not properly dispose SharePoint objects then you can get error like this: "Detected use of SPRequest for previously closed SPWeb object "

SPDisposeChecker is a very good tool to detect memory leaks in SharePoint 2010. First download

Out of the box SharePoint workflows

In this article we will discuss about the out of the box sharepoint workflows. Also you can check my last article on how to create a sequential workflow using Visual studio 2010 in SharePoint 2010.

SharePoint provides six workflows out of the box that end users can configure on their sites. And we do not need any developers knowledge to configure this workflows. We can configure these workflows using interface.

These out of box workflows are avilable according to the SharePoint 2010 version. In the free version