Hi Recently we have started looking into WF foundations and we have a number of web applications in ASP.NET that would drive the workflows. I have couple of questions about best practises in integreating ASP.NET with WF. Where should tracking and persistence tables be placed? Inside the main web application? Outside of it? Should each application have seperate tracking and persistence database? or can it be shared by various web applications? What design pattern/application architecture is mostly recommended for ASP.NET with WF? Do you know of some good reference or sites on the net I could get some easy to follow guides? I am using Nettiers in my apps. Is there any good doco on Nettiers that can explain how to drive workflows?
1. I personally would built multiple layers, a data layer, a security layer, etc... I would definitely not put any important info into the web application. Have a backend that feeds the web app - so the WF can do its job (rendering the views). 2. Nope, I would have one application, one database, multiple DLL's. 3. The standard patterns, its just application development... my personal favorites are the strategy, factory, adapter, and ofcourse the singleton 4. Get the Head First Design Patterns... a must read. Otherwise the MSDN lib and millions of google searches. 5. Not sure what that is.