{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 我命由我不由天 的问题《Should I bother learning Windows Workflow?》','https://www.manongdao.com/q-510947.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Okay, so I've learned WPF and WCF and that was great. I didn't bother with CardSpace because it's probably not gonna take off.
Should i bother with Workflow,..is it worth it? What's the big deal?
相关问题
- Generic Generics in Managed C++
- How to Debug/Register a Permanent WMI Event Which
- 'System.Threading.ThreadAbortException' in
- Bulk update SQL Server C#
- Should I use static function in c# where many call
I originally really liked the concept of workflows, but in the end I think I'll just use something like stateless or roll my own statemachine, and use a database for persistence. My biggest issue with it right now is that there still seems to be a huge memory leak in the workflow runtime. Makes me kind of nervous.
Thanks for all the advice guys. Cheeso get's the answer since he got the most up votes but all opinions are appreciated. I think I'll take Scroll Lock's advice and wait until v4.0 until I take a serious look.