|
Really??
These are the steps to reproduce and workaround the problem:
Step 1. Run a VisualBuild script that attempts to compile MyProject.vbp. It fails and reports that it can't find a component.
Step 2. Imediately open MyProject.vbp in the VB IDE and compile. This time it will compile successfully. At this point MyProject.vbp has also been updated to point to the correct location of the registered components it uses.
Since I've not performed any re-registration of components between Steps #1 and #2 doesn't it imply that its the file locations in MyProject.vbp that are used by the command line compiler?
Also if I check-in MyProject.vbp after step 2 and re-run the VisualBuild script it compiles successfully. Again, no re-registration of components.
|