1

When compiling a particular solution in Visual Studio 2015 using IncrediBuild 7.31 it always insist on rebuilding the entire solution even when no files have changed. I only see this behaviour for the solution on a particular (older) branch.

I have used the setting from the answer to VS2010 always thinks project is out of date but nothing has changed: "Tools->Options->Projects and Solutions->Build and Run->MSBuild project build output verbosity": Diagnostic. This gives me output like this:

1>Project not up to date because the following 36 build inputs were missing:
1> up to date is missing: 'C:\PROGRAM FILES (X86)\XOREAX\INCREDIBUILD\MODULECACHE\220C7\11AC8\C1.DLL'
1> up to date is missing: 'C:\PROGRAM FILES (X86)\XOREAX\INCREDIBUILD\MODULECACHE\220C7\11AC8\C1XX.DLL'
1> up to date is missing: 'C:\PROGRAM FILES (X86)\XOREAX\INCREDIBUILD\MODULECACHE\220C7\11AC8\C2.DLL'
1> up to date is missing: 'C:\PROGRAM FILES (X86)\XOREAX\INCREDIBUILD\MODULECACHE\2B0E5\11AC8\C1.DLL'

Does anyone know how I can avoid that the compiler thinks that "Project not up to date"?

Community
  • 1
  • 1
nielses
  • 150
  • 1
  • 6

1 Answers1

3

Removing the /Bv flag solves the problem for me. (It turns out that a colleague of mine had fixed it in the newer branch.)

I consider it a bug in IncrediBuild.

nielses
  • 150
  • 1
  • 6
  • 1
    Hi nielses, my name is Dori and I'm from the IncrediBuild team. This is the first time we hear about this issue and will appreciate if you could approach our support at support@incredibuild.com to receive instructions on how to send us an extended log so we can address the problem you report in a proper manner. Disclaimer - the writer works at IncrediBuild – Dori Mar 22 '17 at 14:42
  • Thank you, but actually my colleague explains that "he sent our diagnostic build log files to Xoreax, and they told him to remove /Bv". So thanks to IncrediBuild support for resolving this. You might have our specifc case in your records. – nielses Mar 22 '17 at 18:25