Originally Posted by
BlackBox
You may have already mentioned this, but can you successfully debug from either VS Express or VS Ultimate?
As I jumped from Visual LISP to .NET (skipping VBA altogether), I'm afraid my usefulness here is running thin... I knew of the Magic Macro to help port VBA to VB.NET, but never bothered with it, as I had no VBA of consequence... Instead, I just started to learn how to port/replicate many of my Visual LISP functions as pure .NET. I did initially start coding in VB.NET as I felt it more familiar to read to that of Visual LISP syntactically, but quickly came to see C# as the stronger language, made the switch, and haven't looked back.
Now, it may just have been a slip of the keyboard, but to verify, you did install the ObjectARX SDK, and AutoCAD .NET Wizard (not the AutoCAD ARX Wizard), correct?
I know it can get confusing, but the ObjectARX SDK provides the managed assembly references needed to build & debug .NET projects (C#, F#, VB, etc.)... If memory serves, VS 2010 Express had separate installations for each C++, C#, and VB, unlike newer VS Express, and now VS Community. Also, keep in mind that you can use a newer VS IDE to develop for older versions of AutoCAD, so long as you've installed the appropriate ObjectARX SDK (and obviously AutoCAD, etc.); I use VS 2013 to build apps for 2010-2015, and now 2016 (in Beta).
In any event, I'm sorry that I've not been able to help - perhaps someone smarter than I will be along to educate us both as to the issue preventing successful debug. Grrr
Cheers