One of the great things about the 1.4/1.5 SDK tools is the validation that is now performed on Windows Azure packages. This makes it easy to check before you deploy things like missing dependencies. As an example, here is a project warning generated when a dependency is not set to be copied local.
One thing that always annoyed me is that it is a warning and not an error. I may have in the past deployed packages that failed, just because I wasn’t looking at the errors.
However you can actually have these warnings block your deployment by setting the “Treat warnings as errors” option on your Windows Azure project to true. (Tip: right click your Windows Azure project, click properties, then click Development.)
Which changes the warnings to errors:
THIS POSTING IS PROVIDED “AS IS” WITH NO WARRANTIES, AND CONFERS NO RIGHTS OR DANCING CATS