.NET
Re: acadentity in vb and Vb.net
Hi,
as long as you use Option Strict (without any exceptions) late-binding would be disallowed. Look at this screenshot, if you set STRICT to ON ==> latebinding will raise an error.
And one more word to that: set the option as global for you project within the project-properties and not within the code-file(s).
Having set that you would not get compiled your code
dim cadEnt as acdentity
i can get
cadEnt.startpoint
Because the object of type "AcadEntity" does not have a property called "StartPoint" (as AcadEntity can reference any geometry-objects, something like AcadCircle or AcadHatch or ....)
If you have a line and want to get it's startpoint you have to use a variable of type AcadLine
If you have a polyline and want to have it's vertices you have to check what type of polyline it is (LWPoly, 2D-Poly, 3D-Poly) and have to use this type to declare the variable.
Of course ... you can remove now option strict and all will be as you mentioned "I have a object from any type, give me the start point" ==> but as long as this object does not have a start point the code will crash.
Even if you have a perfect error handling the crash uses a lot of time, so a lot of performance.
The big disadvantage of having option strict on is that you have to write more code.
The big advantage of having option strict on is your code won't crash because it would even not get compiled. So you see possible problems within your code just while writing it, not if a user selects the wrong object type and then AutoCAD is away with some greetings like "unhandled exception" at the customer.
HTH, - alfred -
