MSDN Magazine March 2007
View Complete Post
This month's column describes how to use WCF for communication between a workflow and a host application in Windows Workflow Foundation 3. This knowledge should help developers with their efforts using WF3 and prepare them for WF4, where WCF is the only abstraction over queues (referred to as "bookmarks" in WF4) that ships with the framework.
MSDN Magazine November 2009
Schema- first contract-first modeling of Web Services gives you the ability to model your contracts with an XML-centric mindset. This process keeps you focused on universally acceptable types and the hierarchical data structures that can be represented in XML.
Christian Weyer, Buddhike de Silva
MSDN Magazine October 2009
Design patterns provide a common, repeatable approach to solving software development tasks, and many different patterns can describe how to accomplish a certain goal in code. When developers begin working with Windows Workflow Foundation (WF), they often ask about how to accomplish common tasks with the technology. This month's column discusses several design patterns used in WF.
MSDN Magazine August 2009
The heart of Windows Workflow Foundation is its declarative programming model. Here are some best practices to consider when using WF to realize software solutions in the real world.
MSDN Magazine December 2008
With the NET Framework 3.5, Windows Workflow Foundation can now truly be integrated with Windows Communication Foundation. This column describes how the integration works and how to make use of it effectively.
MSDN Magazine Launch 2008
State Machine workflows represent a different way of visualizing program logic. Rather than flowing from activity to activity like sequential workflows, State Machines transition from state to state. Learn about uses for State machines and see how to design and build a State Machine workflow with Windows Workflow Foundation.
MSDN Magazine February 2008
Due to the distributed nature of a business process it makes sense for a workflow to be deployed as a distributed application. See how Windows Workflow and Web Services hold the key.
MSDN Magazine October 2006
In last month's column, I presented a helpdesk workflow sample that focused on WindowsÃÂ® Forms client applications. This month I'll discuss ASP. NET workflow applications and the ability to expose a workflow as a Web service and invoke a Web service from a workflow.
MSDN Magazine April 2006
In the January 2006 issue, Don Box and Dharma Shukla introduced WindowsÃÂ® Workflow Foundation and discussed the overall architecture of the framework and its constituent components (see WinFX Workflow: Simplify Development With The Declarative Model Of Windows Workflow Foundation).
MSDN Magazine March 2006
Windows Workflow Foundation allows you to write workflow-based programs in terms of domain-specific activities that are implemented in CLR-based programming languages such as C# and Visual Basic. Here Don Box and Dharma Shukla get you started.
Don Box and Dharma Shukla
MSDN Magazine January 2006
I need a detailed instruction on how to upgrade From Upgrading from Windows SharePoint Services 2.0 (SBS 2003 ) to SharePoint Foundation 2010.
Background of the case:
I have all my databases (STS-database and STS_Config) saved but, I forgot to save my Virtual Site )Companyweb site) and I mistakenly re-installed IIS on the SBS 2003, hence I lost the companyweb site. Is this an issue to migrate to Sharepoint foundation
2010. The Sharepoint foundation 2010 is running on a Microsoft HyperV Server 2008 R2
Also, I have created a Virtual 2003 SRV ENT with Sharepoint Services 3.0 running on it. I also have attached my Databases STS_Database and STS_Config)... how do I get it working like a regular website. I have modified the CNAME record to reflect the new server...
http://companyweb - it take me to the new site but it loads a blank page. I did create a new CompanyWeb Virtual site on the VHD 2003 server.
Your help is greatly appreciated.
Thanks for your prompt response. Nelson
I see that SQL Server 2008 R2 Reporting Services now supports
Claims Based Authentication in Sharepoint 2010, meaning that end users can authenticate with Sharepoint using Claims Based Authentication, and use the same security tokens to connect through to Reporting Services.
I assume that behind the scenes Sharepoint is using
Windows Identity Foundation (WIF - formerly codenamed "Geneva") to handle the authentication, and passing this on to Reporting Services.
I'm keen to use Windows Identity Foundation to authenticate with Reporting Services
without Sharepoint. We have an existing ASP.NET web application, and we'd like to call Reporting Services from that, passing on the Windows Identity Foundation credentials of the user logged into our web application.
I've done some work on setting up a custom security extension using Forms Authentication (based on the
sample), but am not sure how to proceed from there.
Google/Bing hasn't been helpful. Can you please point me to some guidance on how to set up Windows Identity Foundation authentication for Reporting Services?<
We are currently an ISV evaluating WF4 for use as a Rules/Workflow engine, possibly intending to use the 'Forward-chaining' rules engine from WF3 in WF4. We currently have no WF assets.
We need to understand what the production environment footprint would be for WF4 and/or WF3.
I cannot find any useful info easily, so my questions are as follows,
1. What Server versions support WF4/3? W2003, W2008 etc
2. If I host my workflows in IIS what version of IIS will I need?
3. I have not got too far into WF yet, but I assume there are various datastores, what is the minimum version of SQL server I would need?
Thanks for you help