Note that there are some explanatory texts on larger screens.

plurals
  1. POUnable to build solution incrementally: Input file ".NETFramework,Version=v3.5" does not exist
    text
    copied!<p>I'm not able to build solution incrementally. I checked diagnostic log and I found that every project containing workflows are always rebuild because of this: </p> <p><strong>Input file ".NETFramework,Version=v3.5" does not exist.</strong></p> <p>Workflows are always recompiled, new temporary files are created and project is build again.</p> <pre><code> Building target "WorkflowCompilation" completely. Input file ".NETFramework,Version=v3.5" does not exist. Using "CompileWorkflowTask" task from assembly "System.Workflow.ComponentModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35". Task "CompileWorkflowTask" No files found with '.xoml' extension in the set of input files. Generated temporary code file: C:\Users\Ludwo\AppData\Local\Temp\uwdnm5th.cs Workflow markup validations completed with 0 errors and 0 warnings. Done executing task "CompileWorkflowTask". Done building target "WorkflowCompilation" in project "Delta.Workflow.Common.Merged.csproj". Target "CoreCompile" in file "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets" from project "h:\Prj\R4x\M\CountrySystems\Delta\Common\Delta.Workflow.Common\Delta.Workflow.Common.Merged.csproj" (target "Compile" depends on it): Building target "CoreCompile" completely. Input file "C:\Users\Ludwo\AppData\Local\Temp\uwdnm5th.cs" is newer than output file "obj\Debug\Delta.Workflow.Common.pdb". </code></pre> <p>I'm building my projects using MSBuild 4.0. My projects are set to build with v3.5 TargetFrameworkVersion, unit tests projects are build with TargetFrameworkVersion set to v4.0. I tried to build it on different PC but the result is still the same. I also played with references in my projects. It seems to be like v4.0/v3.5 conflict, but I don't know how to fix it. Any ideas?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload