I have finally started to focus my Acad customization by using
.NET API. Although Acad2006 .NET API is based on .NET1.1, it seemed OK to
develop customizatio on .NET2.0 with VS2005, well, until now I was crushed by
Acad2006 (actually AcadMap2006) so hard that I have to think if it is wise to do
the .NET API thing.
My questions is:
With Acad2006, can you really be able to use .NET2.0/VS2005 to
program on .NET API seriously? Is it better to stick with .NET1.1?
Since my all other .NET base app in my office are all on
.NET2.0, I would like make things on the same base. Of course, acad2007's .NET
API is on .NET2.0 and may be more stable than Acad2006 (who knows?).
Howerver, our policy is not going to newest Acad edition to do the free beta
testing for Autodesk. (Just see how quick Acad2007's SP was out: SP1 for just 1
month of release and SP2 for less than a year).
So, my choice would be doing Acad.NET API thing in .NET1.1 for
now, and when we finally get on Acad2007, or 2008, recompile everything on
.NET2.0, or jump on Acad2007 now. This raises another question:
With limited .NET API in Acad2006 and using .NET 1.1, can I
have a stable custom solution (just regular CAD manipulation, most can be do
with VBA)? Or is Acad2007's .NET API is good enough?
P.S.
The reason I have to go to .NET rather than VBA, is that since
AcadMap2006, many AcadMAP specific features are not available in ActiveX
API and may not be there forever.
