
Here’s a summary of some of the hints and tricks I’ve picked up while working with SharePoint Designer 2013 (SPD). Some are to fix issues that SPD introduces itself, and others are just things to make using the tool a little less painful.
.NET development content.


Here’s a summary of some of the hints and tricks I’ve picked up while working with SharePoint Designer 2013 (SPD). Some are to fix issues that SPD introduces itself, and others are just things to make using the tool a little less painful.

Recent versions of SharePoint have exposed a rich tapestry of options for interacting with it without needing to resort to server-side code-based solutions. The main ones that I’m going to talk about here are the JavaScript Object Model (JSOM), SharePoint Web Services, and the RESTful API.

Everyone knows how to create lists via the web browser, but for developers it can often be easier and more controlled to use automation to create lists on target SharePoint sites, for custom solutions they are developing, and the easiest way to do that is often using PowerShell.

Loading (well, reloading) workflows that include Visual Basic expressions in a WCF hosted service is not as straightforward as one might expect. If you have created your XAML workflow based on an ActivityBuilder or a DynamicActivity then the Visual Basic settings aren’t configured automatically.

There may be occasions when you’ll want to save the XAML version of a workflow (root activity) while persisting it. In my case this is normally to ensure that when I persist a workflow and later want to reload it, I’ve got the exact workflow structure I started with. This article discusses how to do just that.

Many ASP.NET 2 projects will have utilised the AJAX Control Toolkit for more dynamic behaviours and the performance gains of partial page refreshes. A common issue with having used that toolkit when upgrading an ASP.NET 2 project to ASP.NET MVC is how to replicate the controls it offered without adding a lot of additional work to the upgrade project.

One of the clear advantages of using Visual Studio for editing workflows over a custom implementation is the readily available auto-completion features of the IDE. A similar style of auto-completion can be added to your re-hosted workflow designer by implementing your own ‘editor service’ and publishing it to the workflow designer control.

The basic re-hosted workflow designer solution described in re-hosting the workflow designer article provides a baseline for a bespoke application that can be used for designing workflows, but without some further enhancements it is quite limited. By default it will only allow you to create and edit workflows that use the Framework’s built-in set of activities.

The basic re-hosted workflow designer solution described in this article provides a baseline for a bespoke application that can be used for designing workflows, but without some further enhancements it is quite limited. A relatively straightforward addition to a re-hosted workflow designer is visual debugging.

In Windows Workflow 4, basic re-hosting of Microsoft’s Workflow Designer WPF control is a simple task. Microsoft has provided a set of controls that can be inserted directly into your own application. This article will guide you through creating your own workflow editor application by re-hosting the System.Activities.Presentation.WorkflowDesigner WPF control.