Paul Andrew

Technical Product Manager for Office 365 at Microsoft

SharePoint Workflow Starter Kit for Software Developers

SharePoint Workflow Starter Kit for Software Developers

  • Comments 3

The SharePoint team originally primarily targetted information workers in providing a workflow development environment for their SharePoint Designer product when they released Windows SharePoint Services v3. For developers who prefer Visual Studio for creating workflows there is now the Workflow Starter Kit as was announced on Randall Isenhour's blog.

I think that software developers will be just as much workflow creators for SharePoint as information workers, if not more.  Workflow in SharePoint is very powerful and it's natural for software developers to want to take advantage of this. But the tools are like a trickle turning to a stream turning to a river. We don't have the river yet, but we also haven't had a release of Visual Studio since the Windows SharePoint Services v3 RTM. I can't wait until that comes around, but until then you want to get one of these packages for Visual Studio 2005.

There are two packages available for the Workflow Starter Kit for SharePoint and VIsual Studio:

MOSS SDK and ECM Starter Kit We combined the ECM Starter Kit with the MOSS SDK documentation and samples, and we also included the WSS and Office Forms Server SDK documentation so you only have to download and install one package.

Windows SharePoint Services Developer Resources If you are only interested in WSS platform development, we combined the WSS SDK documentation with the Workflow Starter Kit.

  • The SharePoint team originally primarily targetted information workers in providing a workflow development

  • Hello, Paul, sorry for offtopic.

    Now I'm getting myself familiar with WWF and I find many ideas from languages such as GPSS and Simula-67. In fact, WWF is, in a some way, Simula  dreamed of.

    Are you familiar with this languages and did you have them in mind when designing WWF?

  • Hi Vasiliy,

    We deliverately set out not to create a new programming language with WF. XAML is a way of modelling parts (known as activities) of a process. Once you have a model of your process you can reason over it and one of the ways you can reason over it would be simulation. We haven't built the simulation engine but it's a natural extension that people could pursue.

    Regards,

    Paul

Page 1 of 1 (3 items)