Long operation causing deadlock message

Mar 22, 2012 at 5:20 PM


I've got a viewmodel that has a quite time-consuming operation that freezes the UI for more then 60 seconds...this causes an exception to appear

The CLR has been unable to transition from COM context 0x1fe458 to COM context 0x1fe5c8 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations

What can I do in order to avoid this? Is there a way of telling caliburn to ignore the fact it's freezing up? Thanks