> > No, I think you will find it should be able to open. Our workflow projects > are very old, and they open just fine. We did upgrade them from .Net 3.5 to > 4.0 last year, but this was literally just a matter of changing the > framework target, there was no other change required. Looking at the > references, they are referencing System.Workflow.Activities and various > other System.Workflow libraries. You can create new workflow projects too > (in .Net 4 or later). > Anyone who has to work in Workflow has my great sympathy though, it is a > horrible technology. >
Sorry for the late reply, I found your emails in spam! The few WWF projects we have are scheduled for replacement, so I'm not wasting time on them. I have VS2015 running in a VM so I can support Silverlight, so I'll just compile the WWF 3.5 projects over there as well. It's luckily not much bother. WWF is a sensible enough idea, but in practise it's rather clumsy and the code gets scattered around the place. One of these workflows sends emails, but I can't easily pin-down where it happens as everything is wrapped in layers of layers. *GK*
