|
Manifests with builds that have project dependencies
Something that I've run into is when you have a project that uses uses an embedded manifest, and that project references another project as dependency, the build is failing from within VBP. The same project compiles fine within the VS2005 IDE itself. The error being returned is along the lines of:
.\MyProject.tmp_Release_Win32.manifest : general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified.
It looks like what's happening is a temporary project is being created, but for whatever reason, it's not creating a temporary copy of the manifest. The workaround is to remove the dependency from the project and simply make sure that it's built seperately. Apparently when there are no other project dependencies, then it doesn't create that temporary project and it finds the manifest correctly.
Any ideas as to how this could be made to work, or is it just a limitation of how vcbuild does its thing?
|