VBA or VBA.net

[Anonymous]

Should I be learning vba 6 or vb.net 2005...Is autodesk's vb editor going to go to the new vb.net?

[GTVic]

Regarding VBA inside AutoCAD:

Note: Autodesk does not have a VB editor, they have a VBA editor - VB and VBA are not very compatible.

I don't know that Microsoft plans on switching from VBA to "VBA .NET". Right now there is no such thing. Potentially it would break many user developed macros in Excel, Word etc. so VBA might be around for a long time.

Regarding Autodesk's other programming interface... I believe Autodesk is in the process of switching from ObjectARX to .NET. That allows you to use C# or VB in the Visual Studio .NET environment.

[Anonymous]

I would say both..
VBA is embeded in many programs
including Office and AutoCAD
and it's going to stay a while longer.

And since can you use the .NET Framework Class Library
from VB and I believe from VBA also
it is a good idea to get to know the framework.

--
Saludos, Ing. Jorge Jimenez, SICAD S.A., Costa Rica

wrote in message news:[email protected]...
Should I be learning vba 6 or vb.net 2005...Is autodesk's vb editor going to
go to the new vb.net?

[Anonymous]

Thanks for clearing that up for me

Patster

[Anonymous]

Jorge,
"it's going to stay a while longer."

So correct. Within the last month I recieved the VBA 6.4 SDK to enable me to evaluate the benefits of integrating VBA into our applications.

Have you looked at how VBA 6.3 is changing? If you have a chance take a look at the CreateObject method and other enhancements.

CreateObject now lets you specify a machine name as an optional argument, which allows developers to create objects on remote machines using DCOM. This now allows for creating distributed, n-tier applications much easier by a machine. A component's location is now a simple function argument. This is a strong benefit to DCOM cross machine boundaries complications.

Another benefit is modeless userforms: User Forms, the custom dialog box designer that ships with VBA, now supports modeless dialog boxes. Developers can now create dialog boxes that can be displayed and used simultaneously as the host application.

Hope this extends the wall of aptitude for this topic.

Regards,

Bob Coward

[Anonymous]

Oh yes, and COM will stay more than a while longer.!
That's why the .net framework was made with the interop capability.

--
Saludos, Ing. Jorge Jimenez, SICAD S.A., Costa Rica


wrote in message news:[email protected]...
Jorge,
"it's going to stay a while longer."

So correct. Within the last month I recieved the VBA 6.4 SDK to enable me
to evaluate the benefits of integrating VBA into our applications.

Have you looked at how VBA 6.3 is changing? If you have a chance take a
look at the CreateObject method and other enhancements.

CreateObject now lets you specify a machine name as an optional argument,
which allows developers to create objects on remote machines using DCOM.
This now allows for creating distributed, n-tier applications much easier by
a machine. A component's location is now a simple function argument. This
is a strong benefit to DCOM cross machine boundaries complications.

Another benefit is modeless userforms: User Forms, the custom dialog box
designer that ships with VBA, now supports modeless dialog boxes.
Developers can now create dialog boxes that can be displayed and used
simultaneously as the host application.

Hope this extends the wall of aptitude for this topic.

Regards,

Bob Coward