We’ve been making significant investments in Workflow since the release of .NET 4, and now that we’re starting to wrap up some of these investments, I thought it would be worthwhile to provide a summary.
The work falls into 3 major areas:
- Improvements in Windows Workflow Foundation in .NET 4.5 and Visual Studio 2012, which has just reached RTM!
- Enhancements for running Windows Workflow Foundation in Azure
- Support for the new workflow capabilities in SharePoint 2013 and the next version of Office 365
A brief overview of each:
This has been a very customer-focused release mapping directly to the feedback we got from customers using WF in .NET 4. We made investments across the runtime, activities and the designer. I’ve blogged about this work previously, but here’s a quick recap.
You can watch this recent TechEd presentation to see these features in action. .NET 4.5 is an in-place upgrade to .NET 4, so when you install .NET 4.5, your existing apps keep working and you get access to all these new features!
One thing that I’m not covering in this post is AppFabric Server. I’m planning a follow-up post regarding the workflow capabilities in AppFabric.
WF in Azure
Generally, what you do with WF on Windows Server today will also work in Windows Azure. However, there have been a few challenges along the way:
- Initially, Azure roles did not have some of the WF-related machine.config entries that you would typically see on Windows Server. This required you to do more config work, particularly for running WCF Workflow Services. These issues have been addressed with updates to the Guest OS images in Azure.
- As shipped in .NET 4, the WF stored procedures for the SQL persistence store used some features from SQL Server which are not supported in Windows Azure SQL Database (formerly referred to as SQL Azure). To address these issues, we updated the runtime and stored procedures in .NET 4 Platform Update 1, which is now part of the Azure Guest OS images. These capabilities are also now rolled into .NET 4.5.
- Due to differences in how the host name is determined on Azure web roles, there has been an issue with hosting WCF Workflow Services in IIS in Web roles. We have made a fix for this in .NET 4.5, which will be available to you when Windows Server 2012 is available in Azure.
For more information on using WF in Azure roles today, you can watch this TechEd presentation.
Workflow Manager and SharePoint Workflows
Another key investment we’re making in this release wave is in support of SharePoint 2013 Workflows. SharePoint 2013 Workflows are now built on WF 4.5 and run in our hosting environment, as opposed to within SharePoint itself. To provide a high scale, multi-tenant environment for workflows on-premises and in Azure, we have developed the “Workflow Manager”. I’ll be following up with a post on Workflow Manager, but until then, you can read more about SharePoint 2013 Workflows here.
Hopefully, it’s clear the team’s been pretty busy delivering new workflow features and responding to your feedback! We’ve landed the .NET 4.5 and Visual Studio 2012 work, but we’re still busy landing the SharePoint Workflow release. We’ve also started planning for our next wave of releases. There are a lot of new features and scenarios we’d love to go after, and we’d would welcome your continued feedback and priorities on our UserVoice site.