You create a SharePoint action to add custom buttons to the ribbon or settings pages. Actions can be created in Visual Studio and consist of a single Elements file. Multiple actions can be deployed with just one file. In typical SharePoint style, a web-level feature is used to install the action(s).
So you want to build a sand castle, but you’re using Sandbox Solutions. Next, the question may come up about Farm solutions. You may ask yourself, "What are the differences?" In this blog post, I'll cover the differences and advantages of Sandbox Solutions vs. Farm Solutions. The goal of this post is to not only introduce you to idea of SandBox Solutions and Farm Solutions but also address the issues associated with each.
One of the more interesting challenges contractors for public sector clients have is working with older versions of software. On a recent project involving an integration of a solution I'd written using Microsoft Dynamics CRM 2016 and SharePoint 2010, I found myself struggling with an issue around capturing a digital signature.
As a straight SharePoint development project, this can be fairly routine: leverage Microsoft Word and its implementation of signature blocks, similarly leverage SharePoint's out-of-the-box (OOTB) workflow for collecting signatures, and you're basically done.
However, the client in question was less than enthusiastic about SharePoint as a platform in general and, because of that, and a few other design criteria, the bulk of the solution wound up being built in Dynamics CRM and SharePoint was largely a simple document repository.
So, how do you not re-invent the wheel for digital signatures and still keep most of your smarts on the Dynamics CRM side? [Bear in mind the production environment where this was going to be enabled was very locked down. Farm solutions were prohibited, so even if you wanted to write your own custom workflow using .NET workflow, you couldn't because that requires a farm solution.]
We have the OOTB workflow already and we can associate it with the document library in question, but what we really needed was the ability to notify CRM when that workflow completed. Answer: SPWorkflowEventReceiver.
There is a lot of documentation out on the Internet that showcases development of add-ins with code samples. In this 5 part series, I want to do the same but also shed some light on the development process from end to end. Before we go any further, I would like you to pay careful attention to a part of the title: SharePoint-hosted. Note that I will not be tackling provider-hosted add-ins in this series. Provider-hosted add-ins are a great platform for development, but there are some intricacies that can be best understood after learning how SharePoint-hosted add-ins work.
Amazon Web Services offers certification testing for IT professionals interested in advancing their careers in the Amazon realm.
In September 2015, I completed the certification exam for the AWS Certified Solutions Architect - Associate. It is by far one of the most difficult certification exams I have ever taken. The exam is designed to measure your "technical expertise in desinging and deploying scalable, highly available, and fault tolerant systems on AWS."
It seems no matter the number of SharePoint farms I've installed and configured, I never seem to breeze through the setup of User Profile Service like I hope. I am the type of person who believes in going for the latest and greatest, which is why I naturally tend towards the FIM-based User Profile Sync Service for connecting UPS to Active Directory. If you go into the User Profile Service Application configuration page, you will notice that option is available along side the good old AD Import method.
One of the easiest ways to deter users from your website is to provide them with a frustrating experience. Be that with broken features, outdated information, or more times than not, an unfriendly user interface. Even the most feature-rich websites will lose users if they don’t have a website that users can access, navigate, and view, no matter what device they’re on. The aim of this post is to help you keep customers by familiarizing you with responsive design and give you the tools to quickly implement these principles in your websites as well as your SharePoint solutions.
It's a simple enough question to ask and answer. In almost every introduction to a foreign language, it's one of the basic phrases we learn. We'll leave aside the irony that we almost never ask the question of another person, because of mobile phones, tablets, and myriad ways which we can answer that question ourselves. As developers, we're often given the task of producing output that includes some date value, usually in a grid or table that provides the user with information about when a particular thing happened.
So far, pretty easy stuff. But I was recently asked to provide users with that information displayed in local time, with some users were scattered over a plethora of timezones. This led to some interesting discoveries I thought I should share below. So grab your sonic screwdrivers, absurdly long scarves, throw the switch on your TARDIS and allons-y!