Warn when trying to deploy over the file:/// protocol,

... instead of failing silently.

Fixes #1650.

Not necessarily the most elegant place to catch the problem ... but it works for me, and from the POV of the user, it's way better then crashing silently.
Okay lets call it good housekeeping then. It's not a problem for the user, but if you deal with a potential exception, generally you don't want to leave the program running just for fun.

Also It'll cause false negatives should we ever deploy any kind of top level error reporting. Again I'm wary of implementing these half fixes and moving on. I'd rather we actually tackle the root of the problem which is that we've allowed the application to be deployed in an unsupported environment.