one difference is that in Water, EBuild does the entire build, including resolving inter-project dependencies etc… in VS, we rely on MSBuild for the core build of the solution (which might contain non-Elements projects), and it just shells out to EBuild for each individual project. As such, the project reference resolving is p to MSBuild and — suffice to say — EBuild is better at it, and many other things ;).
You will probably have to wade thru the MSBuild portions of a more verbose build log to see what fails extractly; my money would be on something not being 100% correct with the project reference — made the Guid doesnt match, or the project file path doesn’t:
shout;t this point to the .elements? (EBuild wot care, if the guid is correct, by MSBuild might).
the Guid looks correct; but it might also be that MSBuild doesnt like if they don’t match in case…
(we auto-capitalize the one sin the project, coz VS sometimes freaks out when they aren’t; maybe I also ned to auto-capitalize the one in the project ref on Import.
How was this project & reference generated?