I've run into problems on numerous occasions of users not having one of the Windows Core fonts installed on their machine (Courier New, Comic Sans MS, Arial for example). Whenever I try to construct one of these it throws an error rather than falling back onto a related, or really, any other font.
What is the best way to construct a Font if I'd like it to be Courier, but I'm not particularly wedded to it?
Well, you could use FontFamily.GenericMonospace to get a Monospace font, instead of specifically Courier:
Font f = new Font(FontFamily.GenericMonospace, 12, FontStyle.Regular);
There are a few more such generic font families as well.
You can also use this as a last resort after trying your preferred font and running into an exception.
This is very unusual. The Windows font mapper will always provide a substitute font when your program requests a font that isn't available on the target machine. That substitute font will usually be Microsoft Sans Serif on XP, Segoe UI on later versions. Neither of those should ever cause a problem.
Then again, if the machine is so messed up that it doesn't have the core fonts available, it might have no TrueType font available at all. Yes, that will bomb your program. Frankly, this isn't something you should have to deal with, unless this is a really valuable customer. It is otherwise trivially solved by your customer's support team.