|
-
August 13th, 2014, 02:24 PM
#1
[RESOLVED] Visual Studios .NET 2003 Strange Build Dependencies
Hello all, it's my first post here, so we'll see how it goes.
As an upfront disclaimer, I'm trying to bandaid a rediculously complicated inherited build process that I would like nothing less than to destroy and use some modern aids, but alas I'm stuck with what I've got and will try to make due 
I've got a solution with 107 projects in Visual Studios .NET 2003, but we will say I've got 26 projects that build in order A->Z. I do a clean, ensure that no files are lurking about to mess with me, then I build.
The build breaks on projects P and Q with errors of "identifier not found, even with arguement dependent lookup", with the dependency being project H which built a ways before. I do a project-only rebuild on H, then a project-only rebuild on P, and no problems. If I do a project-only rebuild on Q at this point, no problem. If I do a solution build (not clean) right after rebuilding P, it will break on Q, again with the same error which is satisfied by H.
None of the other projects build H's code.
Any ideas on:
1) What does the error "identifier not found, even with arguement dependent lookup" actually mean? Google wasn't able to assist.
2) What is causing this strange build dependency?
Much thanks...
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|