With VB.NET (or C# for that matter), you can do two type of Acad
programming:
1. COM automation, which is almost the same as you do in VBA, except for
doing it slower (mainly coding, due to the similar but different syntex,
lacking of convenience provided by Acad VBA IDE...). In my opinion, it does
not make much sense in general to convert VBA to VB.NET code in this
respect. Converting to VB(5/6) ActiveXDLL make better sense. In this case,
you access acad drawing in very similar wya as you do in VBA.
2. ObjectARX .NET API (the main topics of this NG, at least most visitors to
this NG thought so). If you want to do .NET API, you have steep learning
curve both on .NET API and .NET programming itself. The VBA code would be
not convertable (unless you consider re-write entire thing as converting).
You access Acad drawing/object in very different way from VBA. The good
thing is you can still use COM model in .NET API as you do in VBA, if you
really needs it.
So, before you can ask something in detail with VB.NET or C# and expect
someone to answer, first make up you mind: which way to go or which way you
are in: COM or .NET API.
wrote in message news:5750898@discussion.autodesk.com...
I've been doing a lot of programming using VBA for AutoCAD. I want to
convert all this to VB.NET.
Before I insert a block into a drawing, or draw a line on a drawing, I first
have to tell VB.NET to access the active file.
I imagine I have to dimension the drawing, or something, right?
How do I tell VB.NET to access, insert, draw to an active AutoCAD .dwg file?