Recently, I encountered a problem about vs2005's solution file, which is not big but tricky.
This is where things come from. Previously we had a solution for the old version, and then we upgraded the existing system, so there was a new version, however, this new version of solution seems a bit problematic. After the deployment personnel obtain the solution from VSS, they cannot compile the solution using the command line.
This solution is composed of several projects and a website. In fact, the problem lies in this website. At that time, I didn't know where the problem was, and I had no clue, because the query has been checked, there is still no solution. Finally, you can only compare the solution file with the solution file of the previous version to see if there is a significant difference.
The problem was found. You can check it carefully.
The new version is on the left and the old version is on the right.
The projectreferences attribute is available in the old version, but not in the new version. Is it because it cannot be compiled using the command line? So I tried to manually add this attribute to the new version of solution and perform the test again.
This is enough. Now, let's think about it. As a website, you must reference the project. You don't tell it where to find these references. How does it know?