Here’s the updated C# code from the previous post, with the changed lines in red, and here’s the source project.Ĩ // For more information on IMessageFilter:ġ4 InterfaceType ( ComInterfaceType.
We need to implement an additional interface from our WinForm application to make sure it can handle failure (I could probably do with adding that one myself -).Īs it’s hopefully clear: while the problem is likely to be more visible in AutoCAD 2010 once Update 1 has been applied, this is ultimately about correctly inappropriate expectations on the side of the calling application and teaching it to do the right thing. The problem is that – while the VB6 runtime was very good at automatically retrying calls such as CreateObject() – WinForm applications are not. Now we do the right thing and reject the COM call: effectively asking the caller to try again later. If WPF is in the middle of performing some kind of layout processing operation (which leads to Dispatcher.DisableProcessing() being called) and there’s an incoming COM call, then we were previously respecting it which could lead to a crash. This “problem” was introduced as we addressed an issue with the way our WPF components in AutoCAD handle inbound messages, largely due to Microsoft’s decision not to support nested message loops in WPF. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))” (to help people Googling this error message :-). It contains the text “Problem executing component: Call was rejected by callee. NET applications to drive AutoCAD – as shown in this previous post – experiencing intermittent failures once AutoCAD 2010 Update 1 has been applied. We’ve had a few reports from people implementing external.
0 kommentar(er)
