Topic: Overkill Command

[Kerry]

... it is like tits on a bull.

Thanks Tony.
That takes me back about 50+ years to our next door neighbour on the farm.
He was Irish and another of his favourite sayings was 'Take your hurry boy'.

He had 2 daughters, but that's another story altogether.

[TJK44]

I think I found a workaround that appears to work so I don't have to rebuild my project, although I would really like to incorporate Tony's Extension Method 

Code - Visual Basic: [Select]

1.                 Dim curAcadDoc As Object = Application.DocumentManager.MdiActiveDocument.AcadDocument
2.                 curAcadDoc.SendCommand("._-OVERKILL" & vbLf)
3.                 curAcadDoc.SendCommand("_ALL" & vbLf)
4.                 curAcadDoc.SendCommand(vbLf)
5.                 curAcadDoc.SendCommand(vbLf)
6.  

Edit:
I lied, this still does not execute synchronously. Back to the drawing board.

[TheMaster]

I think I found a workaround that appears to work so I don't have to rebuild my project, although I would really like to incorporate Tony's Extension Method 

Code - Visual Basic: [Select]

1.                 Dim curAcadDoc As Object = Application.DocumentManager.MdiActiveDocument.AcadDocument
2.                 curAcadDoc.SendCommand("._-OVERKILL" & vbLf)
3.                 curAcadDoc.SendCommand("_ALL" & vbLf)
4.                 curAcadDoc.SendCommand(vbLf)
5.                 curAcadDoc.SendCommand(vbLf)
6.  

Edit:
I lied, this still does not execute synchronously. Back to the drawing board.

If you're still having problems getting the RunCommand wrapper working, you can also use reflection to call it, without the System.Core.dll problem. 

Here's a post with the reflection-based version:

http://www.theswamp.org/index.php?topic=43113.msg483306#msg483306

[TJK44]

Thanks Tony, that did the trick.