Why is the "reference component" X "not found". considered a warning?

I wonder why, damn it, the VS team thought that it was NOT possible to find a link to the project as a matter of principle?

The specified component "X" was not found. should be seen as a mistake ... and nothing more.

Is there a way (without turning "Treat all warnings as errors") to get this warning as an error in VS2008?

0
source share
3 answers

, . , , . ( ), , .

" " - .

+3

, - ? - , , . , , " ", VS ", , , ".

0

.

- DLL, , ( , VS GUI).

Five links that are not used for the current configuration, despite the fact that they are present on the disk, are always displayed with an exclamation mark in the graphical interface, and this is a warning (which does not appear to contain a warning identifier).

I would really like to “fix” Visual Studio so that it can determine that, due to the configuration that is currently being built, it does not matter that this link may or may not exist (even if it is present).

Seriously, sometimes the Microsoft Nebula makes me get on the wall.
-1
source

All Articles