topic Re: AutoCAD OEM in .NET Forum

AutoCAD OEM

Anonymous — Thu, 03 Nov 2005 17:57:20 GMT

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

Re: AutoCAD OEM

Anonymous — Thu, 03 Nov 2005 23:29:24 GMT

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

Re: AutoCAD OEM

Anonymous — Mon, 07 Nov 2005 19:17:48 GMT

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