The beauty of .NET is that you can choose the API that you use. You can use
NET API, the COM API and the C++ API within the same function.
If you find the .NET API is more difficult to use compared to the COM API
then I recommend that you simply use the COM API. The only thing that you
are going to miss out is the improved performance that you get from the .NET
API.
There's a ease of use/performance trade off that you need to make:
Performance:
Unmanaged C++ API is better than .NET API is better than COM API
Learning curve/ease of use:
COM API is better than .NET API is better than unmanaged C++ API.
The thing to keep in mind is what I said in the first paragraph. You can mix
and match these within the same function so you never have to commit at the
beginning of the project. You can start out with what you feel most
comfortable with and mix in other APIs as you need.
Albert
"john m" wrote in message
news:4851235@discussion.autodesk.com...
Hello,
I wanted to use VB dotNet to make my forms and also for the various
tools for serializing objects.
But it seems very difficult to get a hold of some basic autocad entities
this way.
For example i want to use file dependencies to see if the user has
already accessed the jobdata.xml file i am working with.
what do i need to set a reference to? i see file dependencies in the
object browser but i can't seem to get them to show up elsewhere.
Can i call dotNet constructs from VBA? Or vice-versa?
Is the 2005 beta easier to use with autocad objects?
thanks for any input
jm
