.NET
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AutoCAD OEM

2 REPLIES 2
Reply
Message 1 of 3
Anonymous
387 Views, 2 Replies

AutoCAD OEM

I've just received a demo version of AutoCAD OEM. Since there is no
newsgroup avaiable for this product I thought I'd try here for a little
info. I see that MSVC++ is a software requirement which leads me to believe
that it can only be used with ObjectARX.

But I do see in the documentation that apps can be ported from all other
API's. Does this mean they have to be rewritten using ObjectARX?

Any help would be appreciated.

Dale
2 REPLIES 2
Message 2 of 3
Anonymous
in reply to: Anonymous

Last time I checked, MSVC++ is a requirement. That is because
all DLLs and ARX libraries and other forms of customization that
you supply with the deliverable, must be 'branded', in order for
them to be usable. That is done to prevent the end user of the
product from loading and running their own customization (of any
kind, including LISP, VBA, and so on).

Of course, you can port any kind of customization to ObjectARX,
but that's going to require reasonble experience with it.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com

"Dale Levesque" wrote in message news:5002952@discussion.autodesk.com...
I've just received a demo version of AutoCAD OEM. Since there is no
newsgroup avaiable for this product I thought I'd try here for a little
info. I see that MSVC++ is a software requirement which leads me to believe
that it can only be used with ObjectARX.

But I do see in the documentation that apps can be ported from all other
API's. Does this mean they have to be rewritten using ObjectARX?

Any help would be appreciated.

Dale
Message 3 of 3
Anonymous
in reply to: Anonymous

Ah that makes sense. Thanks Tony.

"Tony Tanzillo" wrote in message
news:5003476@discussion.autodesk.com...
Last time I checked, MSVC++ is a requirement. That is because
all DLLs and ARX libraries and other forms of customization that
you supply with the deliverable, must be 'branded', in order for
them to be usable. That is done to prevent the end user of the
product from loading and running their own customization (of any
kind, including LISP, VBA, and so on).

Of course, you can port any kind of customization to ObjectARX,
but that's going to require reasonble experience with it.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com

"Dale Levesque" wrote in message
news:5002952@discussion.autodesk.com...
I've just received a demo version of AutoCAD OEM. Since there is no
newsgroup avaiable for this product I thought I'd try here for a little
info. I see that MSVC++ is a software requirement which leads me to believe
that it can only be used with ObjectARX.

But I do see in the documentation that apps can be ported from all other
API's. Does this mean they have to be rewritten using ObjectARX?

Any help would be appreciated.

Dale

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th


Autodesk Design & Make Report

”Boost