Windows Workflow Foundation 3
Problems with msbuild and WF mixing .NET 3.0 and 3.5
I have a Workflow project that is in VS 2008. When using MSBuild to build it for publishing, I get the following error: c:\Program Files (x85)\MSBuild\Microsoft\Windows Workflow Foundation\v3.5\Workflow.Targets(34,7): error MSB4067: the element <WFNonResxWithNoCulture> beneate element <ItemGroup> is unreconginzed.I found the following post that had the same problem : https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2206322&SiteID=1My version of System.Workflow.ComponenetModel is 3.0.4203.2123, so I don't think that that is the problem. The workflow project is being built with .NET 3.0 being the Target Framework. At the bottom of the .csproj file are the following lines: <Import Project="$(MSBuildBinPath)\Microsoft.CSharp.Targets" /> <Import Project="$(MSBuildExtensionsPath)\Microsoft\Windows Workflow Foundation\v3.5\Workflow.Targets" />If I change the bottom line to be 'v3.0' rather than 'v3.5', It creates a different problem, and I get this error when attempting to build: Error 42 The "Microsoft.Build.Tasks.Delete" task could not be loaded from the assembly C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Build.Tasks.dll. Could not load file or assembly 'file:///C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, and that the assembly and all its dependencies are available. When I browse to that directory, Microsoft.Build.Tasks.dll does not exist. There is a 'Microsoft.Build.Tasks.v3.5.dll' in that folder. I then started looking closely to the Workflow.Targets file referenced above. There are two directories that I looked at: 'v3.0' and 'v3.5'. The main difference that concerned me is that the file in 'v3.0' directory has a line that the 'v3.5' file does not: <UsingTask TaskName="Microsoft.Build.Tasks.Delete" AssemblyFile="$(MSBuildBinPath)\Microsoft.Build.Tasks.dll" />If i delete this line out of the file at \v3.0\Workflow.Targets, all of my troubles go away. I feel a little anxious about deleting a line in this file, and am wondering what I am changing and what side-effects I have created that I do not know about. Is there any better way to get around this?This initially happened on Server 2008 SP1 with VS2008 and .NET 3.5 sp1 installed, and has been reproduced on a machine with Vista Enterprise SP1 with sp1 for VS2008 and .NET 3.5.Any help or ideas are appreciated.
Hi, Other people have done the same thing as you and it seems removing it did not cause any issues.http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1949553&SiteID=1Thanks,Sung Hon
Error in the Hands on lab 09
How do you load XOML only State Workflow in WFPad for WWFBeta 2.2 (with namespace for codebehind assembly, and activities)?
invoke sub StateMachine workflow
Using WWF to model and support "Tech Trees" in RTS games
RuleConditionDialog and intellisense
Workflow Persistence & Event Arguments
PersistenceService - Transaction Timeout
SQLTrackingQuery from Workflow
CreateWorkflow failing validation
xbox live mic help
download code samples of Microsoft press' windows workflow foundation step by step - Kenn Scribner
Advantage and disadvantage of ASP.NET WorkFl
When do activities CANCEL and How do i force activities to cancel state?