[Mono-bugs] [Bug 324338] Thread.ApartmentState differences with MS

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=324338

User dick at novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=324338#c1


Dick Porter <dick at novell.com> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
                 CC|                                                |jonathan.chambers at ansys.com
         AssignedTo|dick at novell.com                                 |mono-bugs at lists.ximian.com




--- Comment #1 from Dick Porter <dick at novell.com>  2008-04-07 05:13:07 MST ---
I've fixed the exception throwing part in svn r100010

However, someone that understands COM apartment states is going to have to fix
the  behaviour when setting the state of the current thread on the 2.0 profile.
 Modifying your repro slightly to remove the
Thread.CurrentThread.ApartmentState = ApartmentState.Unknown; section shows
that the state stays at MTA throughout without that line.  It seems to suggest
that setting the state to Unknown clears the 'has already been set' state,
contrary to the documentation.  I've also no idea how to tell the COM internals
what to do here.

Reassigning back to general ownership, and CCing Jon Chambers for expert
opinion.


-- 
Configure bugmail: https://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.