<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx</link><description>So I had a use case from a customer to build a sample using BizTalk Server, Windows Workflow Foundation, and Windows SharePoint Services 2003. It was an interesting journey, and wanted to show how I got all these pieces to play nicely. Before diving into</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#535164</link><pubDate>Mon, 20 Feb 2006 02:00:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:535164</guid><dc:creator>Robert Bolton</dc:creator><description>Very interesting and definitely useful. &amp;nbsp;We are currently looking at blending WSS, WWF and BT into our environment. &amp;nbsp;It's my responsibility to do the planning, programming, rollout, etc. for the entire project. &amp;nbsp;But, this stuff intrigues me and seems very straightforward. &amp;nbsp;We're just wondering if we need to configure BT any special way to what we need. &amp;nbsp;</description></item><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#535218</link><pubDate>Mon, 20 Feb 2006 04:52:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:535218</guid><dc:creator>rseroter</dc:creator><description>Hey Robert, &amp;nbsp;if you are using Sharepoint or BizTalk to call a Windows Workflow, you'll have to think about how to host the workflow. &amp;nbsp;That is, if you're doing anything but single-threaded processing, you'll probably want to use a WF service to manage the WF host and provide instances.</description></item><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#536034</link><pubDate>Tue, 21 Feb 2006 17:17:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:536034</guid><dc:creator>Kevin Farley</dc:creator><description>Richard - as always, its a pleasure to read your real-world examples of step-by-step integration solutions.&lt;br&gt;&lt;br&gt;Funny, but we have an embarrassment of riches regarding work-flow here. Note that in the EventHandler itself, you can implement some workflow. Note that with WF we don't need BizTalk, but with BizTalk we don't need WF either (in this case, I mean not in general).&lt;br&gt;&lt;br&gt;I also have had to implement Document Workflow in SPS/WSS with EventHandlers and BizTalk and it was a lot of fun (aka a challenge, but once done, satisfying). Your points on Impersonation are very relevant, this is a key integration point for SPS/WSS.&lt;br&gt;&lt;br&gt;Another useful Integration tying UI to work-flow is the use of Context Menus on the Document library. This is a helpful way to provide seamless integrated UI with the WSS interface, but also a means to send your EventHandler good events. Helpful article here: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/bowerm/articles/175691.aspx"&gt;http://blogs.msdn.com/bowerm/articles/175691.aspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;Thx for the helpful post!</description></item><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#536060</link><pubDate>Tue, 21 Feb 2006 18:07:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:536060</guid><dc:creator>rseroter</dc:creator><description>Thanks Kevin for the comments and insight. &amp;nbsp;Great call on integrating with ContextMenus. &amp;nbsp;Nice idea.</description></item><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#547653</link><pubDate>Fri, 10 Mar 2006 00:32:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:547653</guid><dc:creator>Mark Courtney</dc:creator><description>This is a great example for building a simple workflow using WinWF. &amp;nbsp;Something to consider though is WinWF's applicability to meet the needs of the Enterprise. &amp;nbsp;You will find that using WinWF for multi-stage serial and parallel processes becomes a very cumbersome and ardous task due to the managability and code maintainence involved in rolling out Enterprise level business process automation. &amp;nbsp;Be mindful of when you extend an irrational escaltion of commitment to a framework, when you really need a manageable enterise ready platform for building, deploying and maintaining complex business workflows. &amp;nbsp;&lt;br&gt;&lt;br&gt;You can spend most of your time and resources managing business processes and achieving business results (which is a task in and of itself for most organizations) or spend three times the amount of time and resources managing the code, architectures and the processes associated with complex workflow scenarios. &amp;nbsp;&lt;br&gt;&lt;br&gt;When you have internalized this awareness, feel free to reach out for K2.net - an Enterprise ready BPM platform geared for Microsoft technologies. &amp;nbsp;We take WinWF to the next level, to meet the needs of today's Enterprises.&lt;br&gt;&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://www.k2workflow.com"&gt;http://www.k2workflow.com&lt;/a&gt;</description></item><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#547668</link><pubDate>Fri, 10 Mar 2006 00:41:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:547668</guid><dc:creator>rseroter</dc:creator><description>Don't worry Mark, for &amp;quot;real&amp;quot; human workflow, I still recommend you guys! &amp;nbsp;Since your next release sits on WF, it's good for folks to know the base framework anyway.</description></item><item><title>Windows Workflow in ASP.NET Apps</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#555130</link><pubDate>Mon, 20 Mar 2006 00:03:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:555130</guid><dc:creator>Richard Seroter - SoCal BPI Musings</dc:creator><description>&lt;br&gt;&lt;br&gt;Very very nice article in this month's MSDN Magazine that goes into great depth explaining how to...</description></item><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#603753</link><pubDate>Mon, 22 May 2006 16:07:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:603753</guid><dc:creator>elnomade</dc:creator><description>It's a nice example but It could be better with code and componentes in a .zip file (like MSDN articles). I'll appreciate if you attach these files.&lt;br&gt;&lt;br&gt;Thanks.&lt;br&gt;&lt;br&gt;Leo</description></item><item><title>re: Windows Workflow + SharePoint 2003 + BizTalk Scenario Built Out</title><link>http://blogs.msdn.com/richardbpi/archive/2006/02/17/534406.aspx#603901</link><pubDate>Mon, 22 May 2006 20:02:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:603901</guid><dc:creator>rseroter</dc:creator><description>Hey there, &amp;nbsp;I'd love to be able to provide the code, but most of my demos (this one included) are built for customers and re-purposed. &amp;nbsp;So, I still have to go and strip out customer info and &amp;quot;re-brand&amp;quot; it. &amp;nbsp;For now, feel free to try and rebuild and post questions.</description></item></channel></rss>