So far, I am developing for autocad 2012 using objectarx and VC++ Express edition without problem.
Now I need to develop for Autocad 2006 with ObjectArx, using VC Express edition. I don't need MFC.
I couldn't make it work with VC express 2008, I am currently giving it a try with VC express 2005.
- I installed and updated to SP1 VC Express 2005
- I installed ObjectArx 2006
- I Installed Objectarx wizard 2009: I couldn't install the 2006 one: had the error described in This topic
It works thanks to this post: http://through-the-interface.typepad.com/through_t
I create a basic objectarx project in VC (no MFC, no COM), set the correct paths (include and lib in my project settings), and when I try to compile, I get the error C4430, same as here
I can't find any solution despite my searches, is it really possible to develop objectarx for autocad 2006 with an express VS?
Solved! Go to Solution.
...I can't find any solution despite my searches, is it really possible to develop objectarx for autocad 2006 with an express VS?...
From ObjectARX 2006 SDK Documentation:
..AutoCAD 2006 supports both managed (.NET) applications and unmanaged ObjectARX applications. For managed applications, any development environment that builds applications for the .NET framework is acceptable. For unmanaged applications, the Microsoft Development Environment 2002, Version 7.0, is required.
Because ObjectARX libraries are built with the 7.0 versions of Microsoft's MFC and C-runtime libraries, unmanaged ObjectARX applications built with the 7.1 libraries of Microsoftl Studio .NET 2003 (code-named "Everett") may experience memory-allocation conflicts.
When AutoCAD 2006 attempts to load an application that uses incompatible runtime libraries, it posts a dialog box that lets the user choose whether to allow such applications to be loaded. This behavior applies to unmanaged applications built with Microsoft Visual Studio 6, as well as those built with Everett.
Developers who use the Everett environment for unmanaged ObjectARX development do so without warranty and at their own risk...