I am trying to build about 600 projects, some of them are.net 2.0, some of them are 3.5. I am using Windows 2003 Enterprise Edition 32 bit with all the latest Windows updates.
It builds fine when maxcpucount is 1. If I grab it to try to improve performance, it gets reference errors. When I look at the links to the project where the error came from, they should have been built in order.
Below I gave an example of errors that cause a string violation. Do not hang up project names or relative paths because I changed this so that I have no problems with my employer.
It looks like relative project references cannot be resolved correctly when more than one core builds a solution.
"C:\SVN\MyLibrary\MyLibrary.csproj" (default target) (15) ->
"C:\SVN\FileProcessor\FileProcessor.csproj" (default target) (17) ->
(ResolveProjectReferences target) ->
C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : warning : The referenced project '..\..\Manager\Manager.csproj' does not exist.
"C:\SVN\MyLibrary\MyLibrary.csproj" (default target) (15) ->
"C:\SVN\FileProcessor\FileProcessor.csproj" (default target) (17) ->
(CoreCompile target) ->
FileProcessor.cs(18,39): error CS0234: The type or namespace name 'Manager' does not exist in the namespace 'TheNamespace' (are you missing an assembly reference?)
msbuild . , csproj, msbuild. , . 95% - , - libs