Why doesn't CC.net devenv task fail when a project is missing from the solution?

Question

I've just realised that one of my Cruise Control.net code integration builds has been succeeding despite the fact that a project's missing from the solution (i.e. the solution file points to a project file that's missing from the disk). Does anyone know how to enforce a failure under these conditions?