[Mono-bugs] [Bug 66533][Nor] New - Instantiating a System.Drawing.Font object with a non-existant font throws exception

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by david@quintana.org.

http://bugzilla.ximian.com/show_bug.cgi?id=66533

--- shadow/66533	2004-09-22 03:12:03.000000000 -0400
+++ shadow/66533.tmp.5643	2004-09-22 03:12:03.000000000 -0400
@@ -0,0 +1,48 @@
+Bug#: 66533
+Product: Mono: Class Libraries
+Version: unspecified
+OS: 
+OS Details: XP and FC2
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.Drawing.
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: david@quintana.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Instantiating a System.Drawing.Font object with a non-existant font throws exception
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+Specifying a non-existant font name string in the constructor for a Font
+object causes mono to throw a TypeInitializationException.  However, on
+Windows, .NET 1.1 selects the default system font and keeps going.
+
+Something like the following causes mono to throw the exception:
+
+Font ft = new Font("NonExistantFont", 12);
+
+Happens on Windows and Linux. 
+
+
+Steps to reproduce the problem:
+1. use snippet above 
+2. compile
+3. run
+
+Actual Results:
+TypeInitializationException
+
+Expected Results:
+To be compatible with MSFT .NET, select the default system font instead
+
+How often does this happen? 
+Always
+
+Additional Information: