Office 365 ProPlus – Demystifying the Myths.

Folks who have been tracking Microsoft’s RoadMap Vision for the “Office 365 online” would surely be surprised to see a host of new services (or should I say Jargons) getting added to the bandwagon on a regular basis.  For the sake of those who missed to notice them, here are a few.  Even though I had put them as bullets they do not necessarily mean additional products/services added to the Office arsenal, but some are just added features to make better user experience and achieve more productivity. For instance, the Office graph’s machine learning ability to influence how search results are displayed in Office 365 etc.,

Out of the above list of new rollouts to the Office 365 suite, “Office ProPlus” is an item that should certainly be looked into seriously, as its a paradigm shift from the normal mode of Installing, configuring and maintaining on-premises office applications and certainly is aimed at bridging the gap between the desktop office applications and the cloud based Office 365 solution suite.

Continue reading

727 total views, 1 views today

Install/Configure ASP.NET 5 Environment (DNX, DNVM)

To Install ASP.NET on its own (from a command prompt), we’ll need to first install and configure the environment in which ASP.NET runs, also known as .NET Execution Environment (DNX).  In addition, to setup the DNX we would another tool referred as .NET Version Manager (DNVM), which is used for installing and configuring different versions of the .NET Execution Environment (DNX), depending on whether we need the full .Net Framework or just .Net Core

As a first step, to install DNVM:

  1. Open a new command prompt
  2. Run the below command:

@powershell -NoProfile -ExecutionPolicy unrestricted -Command "&{$Branch='dev';iex ((new-object net.webclient).DownloadString(''))}"

Now type “dnvm” in the command prompt and you should see something like the below:



As a next step:

To install DNX for .NET Core run:

         dnvm upgrade -r coreclr

To install DNX for the full .NET Framework run:

         dnvm upgrade -r clr


915 total views, 1 views today

DNX SDK version ‘dnx-clr-win-x86.1.0.0-beta5’ failed to install. Error when creating a new ASP.NET 5 in VS 2015

After you install VS 2015, when you try to create a new project, on certain machines/desktops you get the below error:

DNX SDK version ‘dnx-clr-win-x86.1.0.0-beta5’ failed to install. The solution will use DNX SDK version ‘dnx-clr-win-x86-1.0.0-beta5’ for this session

The issue is due to the non availability of the powershell 3.0 version in the respective desktop. To solve the error install the PowerShell 3.0 version by following the instructions in the below link:

1,403 total views, 3 views today

SharePoint 2013 Compatibility with IE 11. (Calendar throwing SCRIPT5009 , SEC7111 errors).

When users access SharePoint 2013 site using IE 11, they often are haunted by the following errors:

SharePoint 2013 calendar SCRIPT5009 and SEC7111 errors

  1. SCRIPT5009: ‘HighlightText’ is undefined
  2. SEC7111: HTTP security is compromised by (null)

In addition, you may also see that the “Edit Page” doesn’t render the page in Edit mode, etc.,

However if you try the same URL in chrome it works fine, which is an irony that the opposite would have been understandable!!!

The issue is due to SharePoint 2013’s incompatibility with IE 11, which can be fixed by performing the following:

GoTo IE 11->Tools->Compatibility View Settings -> “Add your site host name”

The above hack would ensure that the site when rendered uses the IE 10 mode (i.e., run in compatibility mode).

2,361 total views, 2 views today

Retain user permission when migrating from Classic mode (SharePoint 2010 ) to Claims Authentication (SharePoint 2013)

The following is the Powershell command to help migrate a site from SharePoint 2010 Classic Authentication to SharePoint 2013 Claims mode along with Retaining the site Permissions defined for users.

Convert-SPWebApplication -Identity “Your Site URL” -To Claims -RetainPermissions

1,073 total views, 1 views today

Using LINQ, Lambda and Expression Trees in .net

LINQ and Expression Trees

Expression Trees represent code in a tree-like data structure.  In LINQ, expression trees represent structured queries that target sources of data that implement IQueryable<T>.  For example, LINQ to SQL provider implements the IQueryable<T> interface, wherein during run-time, when a LINQ to SQL query is executed the underlying implementation leverages the Expression Tree to convert the LINQ query to a “tree like data structure” and then constructs the required output (which in this case is the SQL query), i.e., translate it into a query language appropriate for the data source.  However, on the contrary, when we use LINQ queries to filter data from objects, it returns an IEnumerable<T> which doesn’t use Expression Trees internally.  For instance if you look at the below IEnumerable<T> interface definition,it doesn’t have an Expression defined in it.

Continue reading

1,904 total views, 1 views today

Script Task – Read / Reuse same Recordset twice in a SSIS yields no records or empty

When using a script task/component in SSIS, we often try to read the data from the recordset using an OLEDBAdapter and fill the dataset, like below :

    DataTable dtValidatedResultset = new DataTable();

    OleDbDataAdapter adapter = new OleDbDataAdapter();

    adapter.Fill(dtValidatedResultset, Dts.Variables["User::InputData"].Value);

(The above code uses Script Task and hence it accesses the variable using Dts.Variables collection.  However if you were to use a Script Component, then you would use the strongly typed Variables collection object and access it as Variables.InputData).

However when you use consequtive Script Tasks or Script Components that try to access and read data from the SAME RECORDSET object, the first time it will work fine, but the second time it will read empty records.  This behavior is due to the fact that the Recordset is an ADODB object and has a record pointer / CURSOR that helps to navigate/move between the records.  Since the first time when the Dataset.Fill is invoked, it would have read all the records from the recordset and would have parked the record pointer at the last record in the recordset.

The next time when the same recordset is used in another Script Task/component, it will not rewind or take the recordset pointer to the first record, but would rather try to read it from its current EOR (End of  Record) position and hence you see your DataTable empty.  The only option is to CLONE the RECORDSET before using it again, which would ensure that the original recordset always stays intact for use any number of times in the package.

5,853 total views, 4 views today

PowerShell to perform Visual upgrade of a SharePoint 2010 Upgraded site in SharePoint 2013

Once a Sharepoint 2010 site is upgraded to 2013, the sites will still be rendered in the 2010 mode.  We have two options to upgrade the sites:

  1. Use the Visual Upgrade option in SharePoint 2013, which would in turn create an entry with the SharePoint timer job and will take a minimum of 10-15 minutes (or more depending on the site's size) to upgrade to the new 2013 look and feel.
  2. Use the Powershell and perform the upgrade.

I always prefer the second option, as it allows you to script the Upgrade and perform the visual upgrade sequentially on many sites (especially if you have a parent site collection with 10 or more sub sites in it).  The below is the powershell that needs to be executed to upgrade the site. (Open the SharePoint Management Shell in Administrator mode before executing the below powershell)

Upgrade-SPSite http://<Your_Web_Site_URL> -VersionUpgrade

How to verify if the sites are upgraded?

In order to verify if the sites are upgraded to 2013 look and feel, execute the below PowerShell which will display the site's compatibility level alongside (will either be 14 or 15) to indicate if the site's are upgraded or not: (Open the SharePoint Management Shell in Administrator mode before executing the below powershell)

get-spsite -Limit All


2,489 total views, 6 views today

PowerShell to Upgrade Classic Windows Based SharePoint site to Claims Based Authentication (SharePoint 2013)

During upgrade from SharePoint 2010 to 2013, when we execute the TEST-SPCONTENTDATABASE command, we run into the below exception that says :

"The <Web site> web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode.  There is an inconsistency between the authentication mode of target web application and the source web application.  Ensure that the authentication mode setting in upgraded web application is the same as what you had in previous SharePoint 2010 web application…."

Continue reading

3,969 total views, 6 views today