Porting app to 2005 and few .NET questions

Dear Friends,

We need to switch from AMAP2004 to AMAP2005 and have few questions related to newly introduced .NET compatibility:

1) We have an ActiveX DLL written in VB6 that enables our VBA and VLisp programmers share common AutoCAD routines and functions. Is it going to work the same way as it did in pre-2005?
(we're aware of GetObject changes)

2) Most of the forms being utilized in our apps are ACAD VBA-driven, with few external OCX libraries. Do we have to pay extra attention to OCX and .NET compatibility somehow?

3) Most of our routines are VLisp based, calling above mentioned ActiveX DLL. Is there any change in how VLisp calls external DLLs and deploys it's classes, methods and properties?

4) We also have few ACAD2004 compatible ARX libraries. Do we have to re-compile them using ObjectARX for 2005?

Thanks in advance for any info.

Regards,
Maksim Sestic

 

Maksim,

(1) The automation servers I have written run fine without modifications.
(They were written in Delphi 5, but I don't think this is going to make a difference)

(2) No, as long as you're not using a .NET language. You can continue using your VBA forms and AxtiveX controls as you did before.

(3) No, everything is still the same. Visual Lisp hasn't changed. (In fact, it seems as dead as ye olde Disco)

(4) As far as I know, your ObjectArx applications will run without recompiling. (Unless you're rewriting them in C# or VB .Net using the managed version of ObjectArx)

Note: Have a look at the help files, though. For example, some properties such as "Color" (now "TrueColor") will probably become obsolete in the future. Apps using "Color" still run, but this may change in the next version...

Greetings,
Guido Rooms
Dear Friends,

We need to switch from AMAP2004 to AMAP2005 and have few questions related to newly introduced .NET compatibility:

1) We have an ActiveX DLL written in VB6 that enables our VBA and VLisp programmers share common AutoCAD routines and functions. Is it going to work the same way as it did in pre-2005?
(we're aware of GetObject changes)

2) Most of the forms being utilized in our apps are ACAD VBA-driven, with few external OCX libraries. Do we have to pay extra attention to OCX and .NET compatibility somehow?

3) Most of our routines are VLisp based, calling above mentioned ActiveX DLL. Is there any change in how VLisp calls external DLLs and deploys it's classes, methods and properties?

4) We also have few ACAD2004 compatible ARX libraries. Do we have to re-compile them using ObjectARX for 2005?

Thanks in advance for any info.

Regards,
Maksim Sestic