After my recent switch over to Mac as my main laptop for O365 / SharePoint development, Finally I got an IOS native app running using the O365 IOS SDK and Swift. Nearly after 15 years of development using Microsoft Technologies and Tools, the mobile app development using XCode and Swift rekindles my memory of learning
Introduction SharePoint 2010 Workflow includes an action called Lookup Manager of a User. This action was not included in SharePoint 2013 Workflow. The purpose of this blog post is to show how that action can be achieved in a SharePoint 2013 Workflow. To do so, we will make a call to the REST endpoint for
I recently had to prototype an event receiver that I wrote in my development environment designed to trigger on the migration of data from SharePoint 2007 to 2013 using DocAve Migrator. Since I don’t have DocAve running on my laptop, I basically wrote a couple of PowerShell scripts to simulate what it does. The starting
Having a disclaimer popup in SharePoint is something that is necessary for many businesses and their internal external web sites. This is usually a mandate for legal requirements for tracking legal agreements. Recently we had to add a disclaimer that upon agreement granted you access to the existing extranet site. After reading the disclaimer users would either press ok
After working with Microsoft for over a month to try to resolve an issue where Open with Explorer does not work when access externally through WAP (Web Application Proxy), we finally have a workaround/resolution. The issue comes down to a hand off of authentication between protocols/services. This works properly for almost everything once you have
If you are building a SharePoint 2013 Apps you will need at some point in your development lifecycle to do load testing for your app to see how it will behave under big user load especially if you are building LOB application that you expect to have a big load. This is great but the
As SharePoint Online matures into a viable alternative to its on-premises counterpart, many people are asking the question Which version is right for my organization? As is usually the case, the answer is “It depends”. Too often we see this decision being made solely on one criteria (i.e. cost) and not taking into account all of
I was working on SharePoint 2013 pilot project and I need to integrate customized HTML into Master page for this (publishing site). SharePoint 2013 comes up with new feature called “Design Manager” (This feature available only for publishing site). In SharePoint 2010 we have an option to create a customized master page using SharePoint Designer 2010 (in
Visual Studio allows developers to deploy/publish Apps to a site (site collection) which has been created using the ‘Developer Site Template’. Recently, I was working with a SharePoint 2013 App for one of my customers. The App was developed using Visual Studio 2013 and published on Developer Site Collection (On O365) to test the functionality.
Today, I configured the SharePoint 2013 Farm with 2 WFE and 2 Apps server. Everything went smooth with no issues or errors . Central Admin was working, I successfully created the Search, MMS, User Profile Service and Created 2 Web Apps. Now when I tried to browse the Web App one of WFE was throwing
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]
