http://bugzilla.novell.com/show_bug.cgi?id=604502
http://bugzilla.novell.com/show_bug.cgi?id=604502#c1 --- Comment #1 from Oskar Berggren <[email protected]> 2010-05-10 22:21:28 UTC --- I think major because it breaks RenderAction(), which I believe is a very important part of Asp.Net MVC 2. I don't know any workaround. I tried putting if (ar.AsyncWaitHandle != null) above the call to WaitOne(), and that resolved the issue for me. Thinking further, isn't the idea with this style of asynchronous programming that you are allowed to call the EndXXX() method at any time, and that it will block if it isn't already finished? (Supperted by the "Ending an Asynchronous Operation" section of http://msdn.microsoft.com/en-us/library/ms228963.aspx.) In that case, just removing the call to WaitOne() should be ok. Supposedly, HttpServerUtility should one day implement the asynchronous style fully instead of just blocking, but it would be nice to get this fix in the meantime. Haven't found time to write a test case. And I'm not sure how to go about in doing so, for this case. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
