I want to fail the build if the deployment project issues a warning about missing dependencies.
For example the following is a Warning, personally I think this should be an error as it causes the install to fail as the item missing is a dependency of a custom action.
WARNING: Unable to find dependency 'MyBaseAssembly' (Signature='(null)' Version='2.0.0.13') of assembly 'MyCustomActions.EventLog.dll'
The reason why it can't find it is that version 2.0.0.1 has been added to the project by mistake, so "MyBaseAssembly" appears in the deployment project and the fact that it is the wrong version is a subtle error.
It is easy to treat warnings as errors in class libraries, I just cannot find a way to do it on deployment projects. I would prefer to do it as part of the Visual Studio settings so that the developers see the failure rather than just having the build server pick it up, which it is doing at the moment by opening the log file and hunting through for "WARNING: Unable to find dependency" and failing the build if it finds it.