Visit the Windows Workflow Foundation (WWF) home page and find about nifty stuff like:
- Activity—A unit of work. The work an activity implements can range from very simple to quite complex.
- Workflow—A group of activities that implements all or part of a business process.
- Windows Workflow Foundation designers—Graphical tools that can be used to create and modify workflows and activities.
- Windows Workflow Foundation base activity library—A fundamental group of activities that developers can use to create workflows.
- Windows Workflow Foundation runtime engine—A library that executes workflows. The runtime engine also provides other services, such as mechanisms for communicating with software outside the workflow.
- Host process—A Windows application that hosts the Windows Workflow Foundation runtime engine and any workflows it executes. The host process provides supporting runtime services for persisting a workflow's state, handling transactions, and other functions.
And don't the WWF Architect Dave Green's blog.
Sam Gentile points us to a
post by Paul Wilson, creater of the aptly named
WilsonORMapper, that comments that DLINQ is a poor OR mapper for being the third generation. However, as Drew Marsh
comments, the power of LINQ is that you can build your own ORM into the LINQ product. Hopefully, as David Foderick
points out, there's plenty of time to improve DLINQ itself. ORM gentlemen, start your engines!