Reputation: 23
We are planning to develop a system based on SharePoint 2010 (SP objects, workflows, UI etc.).
The system will contain about a dozen workflows that interact with the SharePoint objects.
From asking around I understood the following:
Upvotes: 1
Views: 337
Reputation: 31641
WF in .NET 4 uses the Interop activity to leverage backwards-compatibility. You can safely execute your existing assets (obviously with some limitations) when the new workflow engine becomes available in SharePoint.
Upvotes: 0
Reputation: 21788
Use .NET 3.5 - otherwise it won't work.
There are some people saying you should not develop State-Machine Workflows because they do not exist in .NET 4, it only has "Flowchart" workflows. But a recent update to .NET 4 re-introduced State-Machine Workflows...
You do not have any other choice right now but to use .NET 3.5. But you should keep in mind that once a new Sharepoint version comes out (SP 2010 is pretty new!), you might have to upgrade your workflows - but in the end you would have to upgrade all code to the new version.
Upvotes: 0
Reputation: 22681
You can only use .NET 3.5 workflows with SharePoint 2010. You are right, .NET 4.0 workflows won't integrate in SharePoint 2010. Don't worry about upgradation, even SharePoint product team would be aware of this scenario. They might either come up with an upgrade tool or a backward compatibility.
Upvotes: 1