[Mono-bugs] [Bug 541402] New: DesignSurface exception when setting the Font property of the surrounding Form

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Sep 23 09:54:52 EDT 2009


           Summary: DesignSurface exception when setting the Font property
                    of the surrounding Form
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: andreas.flucke at t-online.de
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---

Created an attachment (id=319517)
 --> (http://bugzilla.novell.com/attachment.cgi?id=319517)
Testcase.zip (Sources,executable,ccu file,errormessage)

User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR
3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 4.0.20506)

This weird bug occurs within DesignSurface.Flush() (FlushError.txt, given by
ReportFlushErrors). This only happens when the Form is initialized with the
Font property (unnamed.cs line 54). If this line is omitted, everything works
(DesignerLoader produces a file named "generated.cs"). It took me weeks to
track this down...
The appended testcase uses a stripped version of your designer example.
To get rid of the parser, it loads a pre-generated serialized CodeCompileUnit
To reproduce this, you have to modify a property (maybe the name property
"Test" into something else) and
afterwards close the form.

Reproducible: Always

Steps to Reproduce:
1.Run appended "unnamed.exe"
2.Modify "Name" property
3.Close form
Actual Results:  
Serialization Exception

Expected Results:  
Should work independent of the Form properties

This happens in OpenSUSE 11.1 too.

Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list