Top 10 Microsoft Trends to Look for in 2016 – cwoodill

  • Power BI Continues Expansion
  • SharePoint 2016 Is Released
  • NAV 2016 Comes to the Cloud
  • Bundling of Azure Services
  • Machine Learning Solutions for Business
  • SQL Server 2016 Released with New Reporting Capabilities
  • CRM 2016 Released Integrating Recent Acquisitions
  • Microsoft’s Azure Big Data Services Mature
  • Microsoft Goes RAD Again
  • Organizations Lag Behind


Read more…

Author: cwoodil

TOGAF And The Internet Of Things – Avantika Monnappa

TOGAF And The Internet Of Things – Avantika Monnappa

Is TOGAF IoT-Ready?

The Internet of Things is one of the technologies that is addressed by the Open Platform 3.0. The IoT standards from the Open Group will do for IoT what the HTML and the HTTP did for the web, which is enable everything to be connected instantly. Vendors being able to constantly gather information about the customers from their products throughout their lifecycle enabling optimization of maintenance of operations, and providing safety at a lower cost. ItTOGAF_IoT will become much easier for enterprises to monitor and control any installed equipment and integrate it into intelligent solutions.

The Open Group QLM or Quantum Lifecycle Management Work Group works towards providing a framework for the development and consolidation of the open standards that are necessary in enabling the lifecycle management to evolve beyond the traditional limits of the product lifecycle management.

​The IoT work-group has been successful in producing two Open Group IoT standards namely, Open Data Format (O-DF) and the Open Messaging Interface (O-MI), which is currently working on a standard for the lifecycle management of IoT.

Read further this excellent article from Avantika Monnappa
The Open Group Internet of Things (IoT) Work Group

PowerShell for SharePoint Server 2016 Beta 2

PowerShell for SharePoint Server 2016 Beta 2

PowerShell for SharePoint Server 2016 Beta 2


powershell[1]Provides links to articles that explain the Windows PowerShell cmdlets that you can use with SharePoint Server 2016 Beta 2.

Windows PowerShell cmdlets that you use in SharePoint Server 2016 Beta 2 help you complete simple and complex administrative tasks. Command-line Help is available in the SharePoint 2016 Management Shell. For information about Windows PowerShell in general, visit the Windows PowerShell Technology Center.

New and improved features in SharePoint Server 2016 Beta 2

New and improved features in SharePoint Server 2016 Beta 2


Feature Description More information
Access Services New Access features are available when you deploy Access Services in SharePoint Server 2016 Beta 2 . For more information, see Access Services.
Compliance features New compliance features for SharePoint Server 2016 Beta 2 include the document deletion and in-place hold policies. For more information, see Compliance features.
Customized web parts The compile time for customized XSLT files used for Content Query, Summary Links, and Table of Contents Web Parts is improved. NA
Document Library accessibility SharePoint Server 2016 Beta 2 includes new document library accessibility features. For more information, see Document Library accessibility.
Durable links Resource-based URLs now retain links when documents are renamed or moved in SharePoint. NA
Encrypted Connections SharePoint Server 2016 Beta 2 supports TLS 1.2 connection encryption by default. For more information, see Encrypted Connections.
Fast Site Collection Creation The Fast Site Collection Creation feature is a rapid method to create site collections and sites in SharePoint. For more information, see Fast Site Collection Creation.
Filenames – expanded support for special characters SharePoint Server 2016 Beta 2 now supports using some special characters in file names that were previously blocked. For more information, see Filenames.
Hybrid in SharePoint 2016 Hybrid in SharePoint Server 2016 Beta 2 enables you to integrate your on-premises farm with Office 365 productivity experiences, allowing you to adopt the cloud at your own pace. For more information, see Hybrid in SharePoint 2016.
Identify and Search for sensitive content SharePoint Server 2016 Beta 2 now provides the same data loss prevention capabilities as Office 365. For more information, see Identify and search for sensitive content in both SharePoint 2016 and OneDrive documents.
Image and Video previews You can now preview images and videos in SharePoint Server 2016 Beta 2 document libraries. For more information, see Image and Video previews.
Information Rights Management SharePoint Server 2016 Beta 2 provides Information Rights Management (IRM) capabilities to secure information by encrypting and securing information on SharePoint libraries with OneDrive for Business. For more information, see Information Rights Management.
Large file support SharePoint Server 2016 Beta 2 now supports uploading and downloading files larger than 2,047 MB. For more information, see Large file support.
MinRole MinRole is a new feature in SharePoint Server 2016 Beta 2 that allows a SharePoint farm administrator to define each server’s role in a farm topology. For more information, see MinRole farm topology.
Mobile experience SharePoint Server 2016 Beta 2 offers an improved mobile navigation experience. For more information, see Mobile experience.
New controls for working with OneDrive for Business SharePoint Server 2016 Beta 2 provides controls at the top of your personal document folders that make common tasks in OneDrive for Business more accessible. For more information, see New controls for working with OneDrive for Business.
New Recycle Bin in OneDrive and Team sites SharePoint Server 2016 Beta 2 adds a link for the Recycle Bin in the left navigation area of the OneDrive and Team sites. NA
Open Document Format (ODF) SharePoint Server 2016 Beta 2 adds support for Open Document Format (ODF) files to use in document library templates. For more information, see Open Document Format (ODF) available for document libraries.
Project Server New Project Server features are available in SharePoint Server 2016 Beta 2. For more information, see Project Server.
ReFS file system support SharePoint Server 2016 Beta 2 now supports drives that are formatted with the ReFS file system. For more information about the ReFS file system, seeResilient File System Overview and Resilient file system.
SharePoint business intelligence SharePoint Server 2016 Beta 2 now supports SQL Server 2016 CTP 3.1 and the Power Pivot add-in and Power View. For more information about SharePoint business intelligence, see Power Pivot add-in and Power View are now available to use with SharePoint Server 2016 Beta 2.
SharePoint Search SharePoint Search Server Application has significant changes to its deployment. For more information, see SharePoint Search Server Application.
Sharing improvements SharePoint Server 2016 Beta 2 has many new sharing improvements available. For more information, see Sharing improvements.
Site Folders view SharePoint Server 2016 Beta 2 provides a new Site Folders view that lets you access the document libraries in sites that you’re following. For more information, see Site Folders view.
Sites page pinning This new feature helps you see and follow sites. For more information, see Sites page pinning.
SMTP Connection Encryption SharePoint Server 2016 Beta 2 supports sending email to SMTP servers that use STARTTLS connection encryption. For more information, see SMTP Connection Encryption.
SMTP ports (non-default) SharePoint Server 2016 Beta 2 adds support for SMTP servers that use TCP ports other than the default port (25). For more information, see Use SMTP ports other than the default (25).
Web Application Open Platform Interface Protocol (WOPI) You can now rename files, create new files, and share files from within the WOPI iframe on the browser page. NA


Full article…

SharePoint Search for Public Websites

SharePoint Search for Public Websites

SharePoint Search API

SharePoint Enterprise Search capabilities are exposed for use from SharePoint Apps and external Applications through various interfaces. While some of these APIs needs SharePoint context, REST based APIs on the other hand can be accessed directly.

Following are the different API options available.

API name Class library or schema and path
.NET client object model (CSOM) Microsoft.SharePoint.Client.Search.dll
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\ISAPI
Silverlight CSOM Microsoft.SharePoint.Client.Search.Silverlight.dll
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\LAYOUTS\ClientBin
JavaScript CSOM
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\LAYOUTS
Representational State Transfer (REST) service endpoints http://server/_api/search/query
Server object model Microsoft.Office.Server.Search.dll
%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\ISAPI

If .NET client object model (CSOM) or JavaScript CSOM are used on the client, the server would require to have SharePoint Server 2013 Client Components SDK installed. Which can be downloaded at

API selection matrix



Search in SharePoint 2013 includes a Search REST service you can use to add search functionality to your client and mobile applications by using any technology that supports REST web requests. You can use the Search REST service to submit Keyword Query Language (KQL) or FAST Query Language (FQL) queries in your apps for SharePoint, remote client applications, mobile applications, and other applications.

The Search REST service supports both HTTP POST and HTTP GET requests.

GET requests

Construct the URI for query GET requests to the Search REST service as follows:


For GET requests, you specify the query parameters in the URL. You can construct the GET request URL in two ways:



POST requests

You construct the URI for query POST requests to the Search REST service as follows:





When you make a call to the Search REST service, you specify query parameters with the request. Search in SharePoint 2013 uses these query parameters to construct the search query. With a GET request, you specify the query parameters in the URL. For POST requests, you pass the query parameters in the body in JavaScript Object Notation (JSON) format.

Sample GET request:


Sample POST request:


‘__metadata’ : {‘type’ : ‘Microsoft.Office.Server.Search.REST.SearchRequest’},
‘Querytext’ : ‘sharepoint’



The Search REST service includes a Suggest endpoint you can use in any technology that supports REST web requests to retrieve query suggestions that the search system generates for a query from client or mobile applications.

The URI for GET requests to the Search REST service’s Suggest endpoint is:


The query suggestion parameters are specified in the URL. You can construct the request URL in two ways:



Note: The Search REST service doesn’t support anonymous requests to the Suggest endpoint.

Search on SharePoint public sites


Search and Analytics capability is inbuilt to SharePoint 2013. Analytics in combination with Ranking Models on SharePoint works to automatically process and rank search result sets. Secured SharePoint sites helps to security trim the result sets.



SharePoint public sites accessible to all (anonymous) will have some limitations when it comes to Search capability. Limitations include lack of suggest option and result sets will exclude any results which is secured.

Non-SharePoint public sites

SharePoint Search can be extended on a non-SharePoint public facing website through SharePoint Service APIs.  Refer to Section SharePoint Search API for details.

Enable Anonymous Access to Search API


SharePoint Search API are hosted a SharePoint sites. Follow the instructions below to set up a SharePoint site to host Search API.


  1. Create a publishing site for search access
  2. Configure this site for anonymous access and Basic Authentication: AnonAnon1
  3. Remove restrictions on Client Object accessRemoveRest
  4. Create a new Document Library called “QueryPropertiesTemplate ” at rootweb.
  5. Upload “queryparametertemplate.xml” file to the above Document Library
  6. When Query APIs are called from Wrapper service, pass query param:
  7. In the xml file whitelist search options:QueryProps

TOGAF or not TOGAF – Extending Enterprise Architecture Beyond RUP


by Vitalie Temnenco

Originally published in The Rational Edge this article contrasts the disciplines of enterprise architecture, solution architecture, and business architecture; compares these disciplines to the IBM Rational Unified Process (RUP) and suggests ways to combine them; and advocates applying The Open Group Architecture Framework (TOGAF) in combination with RUP to advance the implementation of enterprise architecture within organizations.

When provided with a problem statement or pointed to a specific user need, a project team equipped with the IBM Rational Unified Process® (RUP®) approaches a solution by creating a Business Case, a Vision statement, and a Software Requirements Specification among other artifacts. These work products and the activities that produce them are well understood within both the technical and business communities. However, the ways in which we conceptualize, prioritize, and select which business problems and user needs to implement in software remains a highly variable process throughout our industry.

This article explores the maturing and increasingly important role of enterprise architecture (EA) frameworks for today’s software development organizations. I begin by contrasting the discipline of enterprise architecture with the solution architecture and business architecture disciplines, while relating them to RUP. Then I explain how The Open Group Architecture Framework (TOGAF) advantageously expands the boundaries for enterprise architecture set by RUP to include enterprise business and IT planning, implementation governance, and other activities. Finally, I propose ways to apply TOGAF in combination with a few other EA frameworks.



Using UserControls inside a Visual WebPart User Control

I was migrating SharePoint 2007 solution built using VisualStudio Extension 1.3 to SharePoint 2010 lately.

One of the important items we had to migrate where obviously the WebParts. Inorder to get the visual capabilities and for many other benefits we’ve used user controls inside webparts.

When moving to SharePoint 2010, I found out that Visual WebParts are doing exactly same as what we were doing all these while, except that now Visual Studio 2010 is intelligent enough to make the user controls part of the deployment.

Eveything was smooth in migrating except the common User Controls we used within the UserControls in WebPart. Yes, when we add new UserControls in the SharePoint 2010 solution, Visual Studio puts them under ControlTemplates folder for deploying it on to ControlTemplates folder under 14 hive (ya 14 hive, or you call it SharePoint root folder).

This will help us deploy this easily. However when you add these user controls within the WebPart usercontrol, render will fail coz Visual Studio puts the path to this folder as ~/_controltemplates/yourWebPartFolder/yourWebPart.ascx and actual physical path is  ~/ControlTemplates/yourWebPartFolder/yourWebPart.ascx

For the Solution to work fine after deploying this path has to be ~/_controltemplates/yourWebPartFolder/yourWebPart.ascx (virtual path under iis to ControlTemplates folder)

Trick to fix the situation is to ……

Rename the folder ControlTemplates to _ControlTemplates under your solution location.