Among other things, I would suggest that the Visual C ++ solution is designed to cover all the source code files for this product. However, thanks to “Include Additional Directories” and C ++’s built-in ability to include absolute and relative paths, you can include files that are not part of the solution (starting with standard C ++ headers).
This can happen both by mistake and as intended. However, to monitor the dependencies and a good overview of which files are the source code of the product and which files are Visual Studio embedded files, it would be great if there was a way to tell which ones are not part of the current solution.
See this example:
- C: /Dev/Projects/Project-A/Project-A.vcproj
- C: /Dev/Projects/Project-A/Project-B.vcproj
- C: /Dev/Projects/Project-A/Project-C.vcproj
- C: /Dev/Projects/Project-A/Project-D.vcproj
If I create a solution containing only Project-A and Project-B , nothing prevents Project-A from including files from Project-C and Project-D . This means that if, for example, I want to distribute this solution, I could ignore Project-C and Project-D.
Can we make VC ++ give a warning about source code files that are clearly not part of the solution - outside, of course, the standard C ++ headers? Or at least provide a complete list of files that are ultimately included in the final library / executable?
Thanks in advance!