Wednesday, January 28, 2015
SharePoint is evolving! Are you?
Posted On Wednesday, January 28, 2015 6:47 AM | Comments (0)
Thursday, October 9, 2014
Office365 - The cloud first Microsoft world!
Posted On Thursday, October 9, 2014 7:35 AM | Comments (0)
Wednesday, October 8, 2014
Analytics Drives Adoption - SPTechCon 2014 Presentation By BrightStarr and Webtrends
Posted On Wednesday, October 8, 2014 9:59 AM | Comments (0)
Mobile support for your Enterprise Intranet
Posted On Wednesday, October 8, 2014 2:30 AM | Comments (0)
Thursday, May 29, 2014
SharePoint 2013 - Power of Apps

Overview of SharePoint 2013 - App Model
Posted On Thursday, May 29, 2014 10:08 AM | Comments (0)
Wednesday, May 28, 2014
Yammer + SharePoint = Social Collaboration

Social Collaboration

Posted On Wednesday, May 28, 2014 10:04 AM | Comments (0)
Saturday, April 13, 2013
CSOM (Client Side Object Model) - Slide deck from my presentation @ SharePoint Saturday Houstom
Here is the slide deck I used today @ SharePoint Saturday Houston:
Posted On Saturday, April 13, 2013 1:46 PM | Comments (0)
Tuesday, April 2, 2013
SharePoint 2013 Apps - Policies and Permissions

As we all start working on apps with SharePoint 2013 it becomes very critical to know how permissions with apps work. 

Firstly, we need to know that both the app and the user need permissions to perform operations spec'd for the app. It wouldn't really matter if I was a Site Admin and tried to write to a list using an App if the app itself didn't have adequate permissions and vice versa. 

Basically the app is making a call into SharePoint by providing the OAuth access token.  SharePoint sees that no user credentials were provided in the request and an OAuth access token is present.  When acting on behalf of a user, the token will include user information, so the context will be the App+User context.

Can I use RunWithElevatedPrivileges with Apps?

So many developers use it but don’t quite understand what the API is doing but that is a different discussion... The answer is NO!

The new app model does away with this impersonation confusion and makes things quite a bit more straightforward because there is no impersonation capability in the API. No the question arises: how do we use the new app model to perform actions when the user doesn’t have permission?  The answer is the App Only Policy. 

Our new scenario of an app performing work that the user does not have permission to means we will use the app only policy.  An OAuth access token is present, and this time the token does not contain user information.  In this case, we are solely evaluating permissions based on the permission of the app and not on the user. The first step is to request permission to use the app only policy in your app manifest by adding the AllowAppOnlyPolicy attribute to the AppPermissionRequests node with a value of true.

This capability is only available to provider-hosted and Azure auto-hosted apps.  It is not available to SharePoint-hosted apps.  In a SharePoint-hosted app, there is necessarily always an app+user context. 

S2S - App Only Context 

Creating a provider-hosted app that leverages only policy using S2S is actually very easy.  The first step is to make sure that you add the AllowAppOnlyPolicy attribute in the app manifest.  The next step is to use the TokenHelper::GetS2SAccessTokenWithWindowsIdentity method, passing a null for the WindowsIdentity parameter.

string appOnlyAccessToken = 

   TokenHelper.GetS2SAccessTokenWithWindowsIdentity(_hostWeb, null);

If the app manifest has the AllowAppOnlyPolicy attribute set to true, this call will succeed and return a valid OAuth access token that does not contain user information.  Once you have the access token, then you can use the TokenHelper::GetClientContextWithAccessToken method to obtain a CSOM client context.

using (ClientContext clientContext = 

    TokenHelper.GetClientContextWithAccessToken(_hostWeb.ToString(), appOnlyAccessToken))


    List list = clientContext.Web.Lists.GetByTitle("Announcements");

    ListItemCreationInformation info = new ListItemCreationInformation();

    Microsoft.SharePoint.Client.ListItem item = list.AddItem(info);

    item["Title"] = "Created from CSOM";

    item["Body"] = "Created from CSOM " + DateTime.Now.ToLongTimeString();





To test this, deploy the app and then log on as a user that only has read permission to the list.  Execute the code, and a new item is created even though the user does not have permission to create items in the list.  The Created By and Modified By fields in the list will reflect that it was only the app’s permissions that were used to create the item.

If we had included a user identity (as the code generated by Visual Studio does by default), then the created by and modified by fields would look a little different, showing that code was executed on behalf of an individual.

ACS - App Only Context

Creating an app-only context with a provider-hosted app using a trust to ACS is just slightly more involved.  A trust to ACS is automatically established when you create your O365 tenant.  If you are self-hosting your SharePoint farm, then a trust to ACS can be established between your SharePoint farm and ACS.

We use a similar approach as before, but this time we need to extract the context token string and validate the token in order to retrieve information such as the authentication realm.  Provided this information, we can now request an app-only token using TokenHelper::GetAppOnlyAccessToken.  Once we have the access token, we can now obtain the client context using TokenHelper::GetClientContextWithAccessToken.

string _hostWeb = new Uri(Request.QueryString["SPHostUrl"]);

string _contextTokenString = TokenHelper.GetContextTokenFromRequest(Page.Request);

//Get context token.

SharePointContextToken contextToken =

    TokenHelper.ReadAndValidateContextToken_contextTokenString, Request.Url.Authority);

//Get app only access token.

string appOnlyAccessToken = 


            _hostWeb.Authority, contextToken.Realm).AccessToken;

Response.Write("<h2>Valid app-only access token retrieved</h2>");

Response.Write("<p>" + appOnlyAccessToken + "</p>");


using (ClientContext clientContext = 

    TokenHelper.GetClientContextWithAccessToken(_hostWeb.ToString(), appOnlyAccessToken))


    List list = clientContext.Web.Lists.GetByTitle("Announcements");

    ListItemCreationInformation info = new ListItemCreationInformation();

    Microsoft.SharePoint.Client.ListItem item = list.AddItem(info);

    item["Title"] = "Created from CSOM";

    item["Body"] = "Created from CSOM " + DateTime.Now.ToLongTimeString();





The result is the same as before… a user that does not have write permission to a list is able to execute the app, which has been granted the AllowAppOnlyPolicy in the permission requests in the app manifest, and the write to list operation now succeeds.

Posted On Tuesday, April 2, 2013 4:37 PM | Comments (0)
How to create a Multilingual Apps For SharePoint 2013 using JavaScript
How do you localize apps?
Using multiple languages in JavaScript code in SharePoint 2013 apps. 
Step 1: Add languages in AppManifest.xml
Update the .resx files, that are used to localize .xml definitions, while JavaScript files are used to localize text displayed on pages with HTML and JavaScript.

Step 2: Add this code to HEAD part of your (app) page:
<script type="text/javascript" src="../scripts/Resources.<SharePoint:EncodedLiteral runat='server' text='<%$Resources:wss,language_value%>' EncodeMethod='HtmlEncode' />.js"></script>

Let's say we want to localize word "All" in French:
Step 3: Add Resources.js file to "Scripts" module in your project
Step 4: Add this code to Resources.js:

function Resources_All() { return "All"; }

Step 6: Add file to "Scripts" module
Step 7: Add this code to

function Resources_All() { return "Tout"; }

That's all. Use it in variable:

var all=Resources_All();

"var all=Resources_All();" will return "Tout" on French SharePoint sites, and it will return "All" for sites in other languages.

Happy Localizing!

Posted On Tuesday, April 2, 2013 4:07 PM | Comments (0)
Thursday, January 31, 2013
BlackBerry 10: 5 cool new features should know before you buy!
BB launched the new BlackBerry Z10 and Q10 and it's new OS 'BlackBerry 10'. 
The platform will be available on both its new phones Z10 & Q10.
The Z10 model features a 4.2-inch touchscreen with 356ppi pixel density and 1280x768p resolution, an 8MP camera that can take 1080p videos, and a 2MP unit in the fron... cool huh!
Here's more it' powered by a dual-core 1.5GHz Krait processor and comes with 2GB RAM. 
It also comes with a 16GB onboard storage and can support expansion up to 32GB via microSD card. 
The Q10 BB has a 3.1-inch SuperAMOLED touchscreen with 328ppi pixel density and 720x720p resolution and the beloved 'Qwerty' keyboard (Z10 looks like it has a similarly laid out touch keyboard). It also has the same dual-core processor and the same 2GB RAM.

What's New? 5 Cool new additions
BlackBerry Hub
Apps like Facebook have been completely integrated with the BlackBerry 10 hub. All emails and notifications from such applications as Twitter and Facebook go to the BlackBerry Hub, a nerve centre accessible with a finger swipe even if you have another application open. One can peek into it and open an email, or return to the previous application without opening the email.

BB Remember
BB Remember is meant to organise content into folders and is integrated into BlackBerry Hub. This feature allows users to flag messages, set due dates, take voice notes, add attachments and find contacts.

BlackBerry Balance
A big asset of BlackBerry 10 is what the company has dubbed the "BlackBerry Balance," a system that allows users to separate professional communications and applications from music, photographs and other personal items. 
For instance, IT managers can prevent personal apps from running inside corporate firewalls, but those managers won't have access to personal data on the device. Such an option means that if a user changes job, his or her former company can disable the device's corporate side without affecting personal data. 

Story Maker
BlackBerry introduced Story Maker, an app to aggregate content such as photos and videos into one stream. BlackBerry Story Maker is meant to allow users to create mini movies and share them on social networks.

Other features
It has multilingual support, and users can flick words with one thumb. Also improved are the picture editor, and a multitude of other features that positions the device both as a consumer device and an enterprise device simultaneously. And now the BBM chat allows you to switch from Chat to Video seamlessly. Apps: The company said that more than 70,000 apps are available for users in the BlackBerry World.

I hope this lives up to the expectations and promises to revive the Canadian Manufacturer's market position/share!

Happy Shopping!
PS: I'm guessing the phone releases in US around march but its already out in Canada and some other countries.
Posted On Thursday, January 31, 2013 4:06 AM | Comments (0)
Monday, November 26, 2012
CSOM (Client Side Object Model) - What's new with SharePoint 2013
SharePoint CSOM
The Client-Side Object Model or CSOM came out with SharePoint 2010. CSOM is accessible through client.svc but all client.svc calls must go through supported WFC entry points (supported entry points are .NET, Silverlight and JavaScript). So a developer would need to use client side proxy objects exposed by either a .NET assembly or a JavaScript library. 

Changes with SharePoint 2013
  • REST Capabilities - Direct access to client.svc
  • New APIs - App Model
REST Capabilities
One of the most important changes to the CSOM with SharePoint 2013 is that the web service entry point of client.svc has been extended to allow direct access  via REST-Based web service calls. This is a really critical change since its going to make the SharePoint platform accessible to any other platform, opening the horizons of integration and collaboration with other REST based platforms and devices. OData (a really popular standard data access API for HTTP-based clients) is supported similar to 2010 but will be a more important aspect of SharePoint 2013 development.

New API's
CSOM for SharePoint 2013 has been buffed up with several new APIs for not only SharePoint server functionality but also an API for Windows Phone applications. For a SharePoint 2010 farm most of the new APIs mentioned below are available only via server side APIs:
  1. Search
  2. Taxonomy
  3. Publishing
  4. Workflow
  5. User Profiles
  6. E-Discovery
  7. Analytics
  8. Business Data
  9. IRM
  10. Feeds
SharePoint 2013 remote APIs being accessible through both CSOM and REST is very important to the new app model where developers can no longer run code in a SharePoint environment nor can they access the server-side APIs. So CSOM plays the savior here.

Also, you can now substitute the alias '_api' in order to reference '_vti_bin/client.svc'.
Posted On Monday, November 26, 2012 4:48 PM | Comments (0)
Monday, November 5, 2012
Must Read: Programming using the SharePoint 2013 REST service
Posted On Monday, November 5, 2012 9:00 AM | Comments (0)
Wednesday, October 3, 2012
SharePoint 2013 Certifications - MCSE
Microsoft Certified Solutions Expert (MCSE): SharePoint.

Yes you read it right :) 

SharePoint 2013 Certifications are here... 
The two certifications mentioned below are expected to be published on February 05, 2013. And will count as credit to the new MCSE certificate. 

Posted On Wednesday, October 3, 2012 1:51 AM | Comments (0)
Tuesday, October 2, 2012
Remove a bad/erroneous WebPart from a SharePoint page
If you've added a poorly written webpart to your 'default.aspx' page, the consequence of this action will be that you won't be able to load the page anymore... Don't be sad, there is still a way to remove the webpart from the page :) (Yes, even removing the webpart from the webpart gallery would not solve this issue).

Steps to fix this:
1. Append the following query string to your URL: ?Contents=1.
Once you've added Contents=1 as a query string to the webpart page's URL it will display the Webpart Maintenance Page. 
Example: http://mysharepointserver/default.aspx?contents=1

2. On that page you can now see the webparts added to the page, delete the problematic webpart.
Now try reloading the default.aspx page... Tadaaa!!! you can view your page again :)

3. Leave a thank you note @ comments section :)
Posted On Tuesday, October 2, 2012 10:28 AM | Comments (0)
Friday, September 21, 2012
Automatically Reset Theme To Default, SharePoint 2010

Manually/Through UI

On the top link bar, click Site Settings.

On the Site Management page, in the Customization section, click Apply theme to site.

On the Apply Theme to Web Site page, select No Theme(Default) from the list.

Click Apply.

Through Script

function Apply-SPDefaultTheme([string]$SiteUrl, [string]$webName)


$site = new-object Microsoft.SharePoint.SPSite($SiteUrl)

$web = $site.OpenWeb($webName)

$theme = [Microsoft.SharePoint.Utilities.ThmxTheme]::RemoveThemeFromWeb($web,$false)





After looking in the SPTHEMES.XML file found in the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033 folder, you do see there is a theme with a theme name of "none". Since there is no "default" theme in 2010. So make sure if you wanna reset it to default you know that there is no default, you need to select 'none' :)

Posted On Friday, September 21, 2012 9:03 AM | Comments (1)
Monday, September 10, 2012
Ensure Future Browser Compatibility - SharePoint Branding

HTML and Future Internet Explorer Compatibility with SharePoint

As new versions of Internet Explorer are released, the way HTML is rendered by the browser could change over time. To address the possibility of changes, Microsoft uses the X-UA-Compatible META tag that targets HTML markup to a specific version of Internet Explorer. The default SharePoint 2010 master pages are set to force current and future versions of Internet Explorer to render HTML in Internet Explorer 8 mode like the following markup:

<meta http-equiv="X-UA-Compatibile" content="IE=IE8" />

The Adventure Works Travel HTML includes the META tag to help ensure future Internet Explorer versions will display the SharePoint HTML properly.

For more information about the Internet Explorer Standards Mode, see META Tags and Locking in Future Compatibility.

Posted On Monday, September 10, 2012 8:43 AM | Comments (0)
Tuesday, September 4, 2012
Working with documents and SharePoint - Best practices
Follow these simple guidelines to make collaboration using SharePoint easier:

1. File Name:

  • While it is allowed to use spaces in your filename (and maybe it seems even logical to do so), don’t use them if your file will end up (or is born on) SharePoint. 

    When you use the “download a copy” functionality, SharePoint will replace the spaces with an “_”. This might (will) result in inconsistency when you upload the “same” file again, since SharePoint will see this as a different file (since the filename is different). 

    I recommend using a filename with Capitalization style naming guideline. For instance: the document “Overall governance model.docx” would be named “OverallGovernanceModel.docx”

  • Use the TITLE field in the office applications to give your document a title (and subtitle and keywords, .) The title column can be used in a view in a library. You can get to the document properties by clicking on 'Office Button/Prepare/Properties'. (Office 2007). This is metadata that is stored with the document, and will remain in the document (even if you exchange this document via e-mail, via an external hard drive). The filename cannot be longer than 128 characters. (and that is IMHO far beyond reasonable) You cannot use any of these characters: ” # % & * : < > ? \ / { | } ~ 

2. Versioning:

SharePoint has a built-in versioning system. You can work with major (published) versions, and minor (draft) versions. Of each of these two document types, you can store a numbers of versions that are kept. Watch out, each version is saved, not only the delta between 2 versions, and this counts to your Site Collection Quota. (Example: you have a Word document with a size of 2 MB. When you keep 5 Drafts this will result in storing (and consuming) 10 MB.
So, don’t call your document “NewUserAccountProcessDRAFTv1.docx”, but “NewUserAccountProcess.docx” and use versioning setting in your library.

  • You can enable views on your library to display the version number.
  • You can enable the version number to be displayed in a Word document.

3. Use Metadata

Use metadata to assign other properties to documents, so it can be easily identified, sorted- or grouped by. 

Posted On Tuesday, September 4, 2012 11:52 AM | Comments (2)
Thursday, August 30, 2012
Benefits of a SharePoint Extranet

Read more @ Benefits of a SharePoint Extranet -

Posted On Thursday, August 30, 2012 6:03 AM | Comments (2)
Tuesday, August 14, 2012
SharePoint 2013 – Workflows.

Workflows in SharePoint 2013

There’s a new Workflow model at the core of SharePoint 2013. It is built on the same OAuth authentication and iFrames model that all new apps must work with. It is a redesigned workflow infrastructure that is built on Windows Workflow Foundation 4 and brings new power and flexibility to workflow authoring in SharePoint 2013.

Rich Workflows: If workflows were a sore point in SharePoint 2010, they've gotten a lot better and seem much more able to handle more complex activities, including looping and working with web services (anyone thinking orchestration?). "A new action that enables no-code web service calls from within a workflow, new actions for creating a task and starting a task process and new workflow building blocks such as Stage, Loop, and App Step". With Azure Workflows you can even do "REST and Service Bus Messaging". Find out more about what is new in workflow in SharePoint 2013 from the Microsoft blog. Finally, machine translation provides automated translation into various languages - I’m looking forward to really seeing what our business can do with this translation service.

· ASP.NET 4.5, SQL 2008 R2, WCF 5.0 and Other new base technologies used


A fully declarative authoring environment enables information workers to use SharePoint Designer 2013 Preview to author powerful workflows, and a new set of Visual Studio 2012 workflow project templates let developers access more sophisticated features like custom actions.

SharePoint 2013 Preview workflows are powered by Windows Workflow Foundation 4, which was substantially redesigned from earlier versions. Windows Workflow Foundation (WF), in turn, is built on the messaging functionality that is provided by Windows Communication Foundation (WCF).

Conceptually, workflows model structured business processes. Therefore, Windows Workflow Foundation 4 workflows are a structured collection of workflow "activities," each of which represents a functional component of a business process.

The workflow platform in SharePoint 2013 Preview uses the Windows Workflow Foundation 4 activity model to represent a SharePoint-based business process. Additionally, SharePoint 2013 Preview introduces a higher-level stage-gate model on which to create workflows.

It is important to note the relationship between workflow activities and SharePoint actions. Workflow activities represent the underlying managed objects whose methods drive workflow behaviors. Workflow actions, on the other hand, are wrappers that encapsulate the underlying activities and present them in a user-friendly form in SharePoint Designer. Workflow authors interact with the workflow actions, whereas the workflow execution engine acts on the corresponding activities.

The activities, which are implementations of activity classes, are implemented declaratively by using XAML.

Workflow activities are invoked using loosely coupled web services that use messaging APIs to communicate with SharePoint. These APIs are built on the messaging functionality that is provided by Windows Communication Foundation (WCF).

Posted On Tuesday, August 14, 2012 7:06 AM | Comments (0)
SharePoint 2013 – Mobile Support.

With the increase in mobile browsing and greater demand for a mobile workforce, I’m pleased to see that SharePoint 2013 offers vast improvements to the mobile browser experience. SharePoint 2013 introduces the new ‘Contemporary View’. Depending on the mobile browser, users have one of the following browsing options, other than the ‘Mobile View’ explained next, here's a link -  to another blog post by my colleague on SharePoint's mobile capabilities:

· Contemporary view: This view offers an optimised mobile browser experience to users and renders in HTML5. This view is available to Mobile Internet Explorer version 9.0 or later versions for Windows Phone 7.5, Safari version 4.0 or later versions for iPhone 4.0, and the Android browser for Android 4.0 or later versions.

· Classic view: This view renders in HTML format, or similar markup languages (CHTML, WML, and so on), and provides backward compatibility for mobile browsers that cannot render in the new contemporary view. The classic experience in SharePoint Server 2013 Preview is identical to the mobile browser experience of SharePoint Server 2010.

· Full-screen UI: There is also the ability to have a full desktop view of a SharePoint site on a smartphone device.

The following figure shows a classic, contemporary, and full-screen UI rendering for a smartphone browser.


Mobile browser redirection

To access a site by using the optimized mobile browser experience, a new feature named Automatic Mobile Browser Redirection must be activated on the site. When activated and a mobile browser is accessing the site, this feature checks the mobile browser to determine whether it can handle HTML5. If the mobile browser supports HTML5, the contemporary view is rendered. Otherwise, the classic view is rendered.

By default, this feature is activated when any of the following site templates are used:

· Team Site

· Blank Site

· Document Workspace or Center

· Project Site

You must explicitly activate the feature on sites created with other templates. You can activate or deactivate Automatic Mobile Browser Redirection at the site level.

Mobile views and the browser definition file

A mobile view is a version of the SharePoint site that was optimized for mobile devices. The browser definition file lists the mobile browsers and devices that are supported by SharePoint Server 2013 Preview and is used to redirect mobile browsers to the mobile views. You can modify the browser definition file to change the redirect behavior of a mobile browser, or to add or delete entries from the list of supported mobile devices.

The browser definition file lists the mobile browsers and devices that can access mobile views in SharePoint Server 2013 Preview. When a user browses a SharePoint site from a mobile device, the mobile browser submits to the site an HTTP GET request that includes a user agent string. If the mobile browser and device model in the user agent string are listed in the browser definition file and the isMobileDevice setting for the mobile browser is set to true, SharePoint Server 2013 Preview redirects the mobile browser to the mobile view of the site. Otherwise, a standard view of the site is shown in the mobile browser. You can modify the file to change the redirect behavior of a mobile browser.

The browser definition file lists the mobile browsers and devices that are supported by SharePoint Server 2013 Preview. The file can be updated when product updates to SharePoint Server 2013 Preview are released. You can also modify the file to add a mobile browser or device to the list. For more information about how to modify the browser definition file, see Configure the browser definition file in SharePoint Server 2013 Preview.

Note: Here’s a List of Supported Mobile Devices by SharePoint 2013.

Yet another cool feature of SharePoint 2013!

Posted On Tuesday, August 14, 2012 7:05 AM | Comments (0)
SharePoint 2013 – Enhanced User Experience, User Interface.

SharePoint 2013 - User Experience, User Interface and a ‘Brandable’ Central Administration

Original Post @

Having been playing around with the preview of SharePoint 2013 for a while now and having blogged a series of articles on individual features and enhancements including SharePoint 2013 search and social features, workflows in SharePoint 2013 and the new SharePoint 2013 App Model, there are so many more improvements that I love. Here are some of the other top features that caught my attention at the first site of SharePoint 2013, related to the SharePoint 2013 user experience, user interface and administration.

The new GUI: SharePoint 2013 adopts Microsoft’s big user interface (Windows 8 Metro) that is easier to use, snazzy, and well, different (in a good way). While there appears to be some uncertainty over the on-going use of the name ‘metro’ to describe its new, radical UI design, there is no doubt that the concept itself will be around for a while. Microsoft are planning to use Metro as the default UI for SharePoint, as well as user tools like Office, Windows, Xbox and mobile devices.

Cleaner messages: With 2013, SharePoint is bringing out a better way to present messages and notifications.

For example:


Is much easier on the eye than:


And even


Is much better than:


‘Brandable’ Central Administration


Yes, you heard/read it right. You can now add branding to even the ‘Ugly’ central administration portal. You will have the same capabilities to include a custom master page, css and images to the central admin site as you would for a publishing portal.

Tablet View

Regular View


Tablet View


Isn’t it cool? Read more on the mobile/tablet view and its benefits in my previous blog about Mobile Browsing in SharePoint 2013.

Drag and Drop documents: Within any document library you can simply drag and drop your documents and files. A simple feature, but I can see it dramatically reducing time taken to add content to SharePoint.


Cleaner and Less Cluttered Ribbon


Easier on the eye context menus

You no longer have to deal with drop downs and weird context menus. SharePoint 2013 bring out much easier to use and better to look at menus which give you appropriate amount of information with the capability to always view more J


Live Doc Preview — By default, there is now a live document preview, not just something you see in search, but available for all documents by default.

Taxonomy Based Navigation — There is now a new way to navigate through a site — using taxonomies based on term stores. You can attach more than one taxonomy to a site, which is good if you want to create navigation for product sections of a website or any navigation that doesn’t follow the site structure.

Security on Term Stores — Want to restrict certain parts of your term store to certain groups? You can do that now by applying permissions to term stores. As this topic is very near and dear to my heart, we’ll provide you a more detailed look at this capability in a later article.

As a closing note, I am really happy that branding has gotten a lift – bigger than anybody imagined probably imagined. May be now users who were not finding SharePoint usable have a change in opinion J. Metro design principles and guidelines have been used to create a cleaner and more responsive user experience.

Posted On Tuesday, August 14, 2012 7:04 AM | Comments (0)
SharePoint 2013 – Social & Enterprise Collaboration.

Perhaps the most exciting changes in SharePoint 2013 relate to enhanced social capabilities. The list of new features is extensive - micro blogs, activity feeds, community sites, following, likes and reputations are the ones that standout the most.

With the new Activity Feeds, I really like the idea that I can get real notifications of what's happening on a site. I really like ‘Following’ function, which adds the ability to "follow" people, sites, documents and topics, with subsequent actions of the followed entity appearing in the user's activity stream. Keeping up to date with the activities of colleagues in SharePoint has never been easier and I can see it really improving employee productivity and collaboration.

I think the new community features will be interesting, with Microsoft’s new site templates I can see an increase in micro-blogging happening within SharePoint; I'm certainly excited to see how our internal communities use them. Find out more about what is new in social computing in SharePoint 2013 on the Microsoft blog.

More collaboration and social integration features that are definitely worth mentioning are:

Communities – ‘Communities’ is a new subsite template that can be used and is based on the wiki pages infrastructure. It leverages discussion groups, likes, ratings.

Categories Categories can be configured per community to allow people to see discussions being had with much more granularity.

Reputation Reputation has been introduced to allow you to rate users within the community from 1 to 5 stars. This is different from 2010 where now the rating is actually stored in the subsite data rather than the social databases in the service application.

Community Badges – Badges are new to 2013. Essentially rules can be set when particular levels are reached in the community as seen from the screen shot below.

As an aside, it is worth noting that the social tools market is hot and feature advances are coming fast and furious. In this environment I do worry that Microsoft's three year product release cycle seems like an anachronism, leaving it constantly lagging behind its competitors.

Posted On Tuesday, August 14, 2012 6:58 AM | Comments (0)
SharePoint 2013 – Search, what’s new?

Search functionality in SharePoint 2013 Preview includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types. Additionally, there have been significant enhancements made to the keyword query language (KQL). A hot topic within SharePoint 2013, below is a summary of some of the enhancements within search in the new version of SharePoint.

Search Engine Optimisation & Analytics: Search has dramatically improved in SharePoint 2013 (see my colleague Marwan’s post specifically about SharePoint 2013 @ Much of this is due to analytics moving into search. The Analytics Processing Component in SharePoint Server 2013 Preview runs different analytics jobs to analyse content in the search index and user actions that were performed on a site, to identify items that users perceive as more relevant than others.

Content Search Web Part: This new web part is cool, but it may take a demo to understand its power. In many ways this is the next generation of the previous Content Query Web Part - "The Content Search Web Part displays content that was crawled and added to the search index. You can use category pages when you want to aggregate content that meets certain criteria or parameters. For example, in an intranet scenario, all company events are maintained in a list that is shared as a catalogue. A query is issued from the Content Search Web Part to return all items from the search indexes that are specified in the query”. (See the Microsoft blog on ‘What is new in web content management for SharePoint 2013’ for more information).

More to follow on Web Content Management features soon, but in the meantime, take a look at my colleague Will’s article on SharePoint 2013 for WCM.

Also worth exploring for Search enthusiasts are these articles:

Manage the search schema in SharePoint 2013

Create and deploy a thesaurus in SharePoint 2013

Overview of Search Schema in SharePoint 2013

Posted On Tuesday, August 14, 2012 6:57 AM | Comments (1)
SharePoint 2013 – Everything is an ‘App’!

Lists, libraries, sites and even calendars are now ‘Apps’. In an interesting move that will at one stroke empower end users, reduce load on overworked IT operations departments and add fuel to the already active after-market for SharePoint add-ons, Microsoft is introducing an Apps Store model with SharePoint 2013.

SharePoint 2013 Preview introduces a Cloud App Model that enables you to create apps. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint. An app has few or no dependencies on any other software on the device or platform where it is installed, other than what is built into the platform. This characteristic enables apps to be installed simply and uninstalled cleanly. Apps have no custom code that runs on the SharePoint servers. Instead, all custom logic moves "up" to the cloud or "down" to client computers. Additionally, SharePoint 2013 Preview introduces an innovative delivery model for apps for SharePoint that includes components like the SharePoint Store and the App Catalog.


This new app model will take you Microsoft into the New Online World – "The new app model embraces web standards: You can develop the user experience with HTML and JavaScript, and leverage SharePoint and other REST services right from the client using JavaScript and JSON. You can even create your own REST services and provide a web hosting platform of your choice to handle complex logic and integration of data and services. The new cloud app model also takes advantage of OAuth to allow for secure communication between SharePoint and remote hosted apps and services."


Why ‘Apps’?

- Provide users with an easy discovery, purchase, and installation process.

- Provide administrators with the safest SharePoint extensions

- Provide you with the simplest marketing and sales system based on a Microsoft-provided online app store.

- Maximise your flexibility in developing future upgrades.

- Maximize your ability to leverage your existing non-SharePoint programming skills

- Integrate cloud-based resources in smoother and more flexible way


- Enable your extension to have permissions that are distinct from the permissions of the user who is running the app

- Enable you to use cross-platform standards, including HTML, REST, OData, JavaScript, and OAuth.

- Enable you to leverage the SharePoint cross-domain JavaScript library to access SharePoint data. Alternatively, you can use a Microsoft-provided secure token service that is OAuth-compliant

- Can extend SharePoint Online websites as well as on-premises SharePoint websites.

Here’s an example of how a user would see apps:

- Need a Calendar on your site/page – Add the calendar app!




Initial SharePoint 2013 app offerings are already being promoted by Microsoft and it will be interesting to see how this space grows with the full release of SharePoint 2013.

Posted On Tuesday, August 14, 2012 6:53 AM | Comments (0)
New with SharePoint 2013 Series

As a consolidation effort and improving readability, I'm going to convert my 3 previous blogs about the new features with SharePoint 2013 into a 7 blog series.

The original posts will be published @ in a series with better structure and formatting :)

SharePoint 2013 – Everything is an ‘App’!

SharePoint 2013 – Search, what’s new?

SharePoint 2013 – Social & Enterprise Collaboration.

SharePoint 2013 – Design and Branding Features.

SharePoint 2013 – Enhanced User Experience, User Interface.

SharePoint 2013 – Mobile Support.

SharePoint 2013 – Workflows.

Posted On Tuesday, August 14, 2012 6:50 AM | Comments (0)