The Help for 2013 has NO reference to AcCoreMgd .DLL.
This seems weird to me because this DLL is the major
change to the API and the reason that managed code requires
a rebuild to work in AutoCAD 2013.
Has anyone seen ANY reference to AcCoreMgd in any of the help files. ?
(please don't point me to Keans blog)
I'll attach a piccy to show what I mean.
Also : Has anyone seen a 'AutoCAD Net Developers Guide' targeting 2013 ??
added: weird, I think this may be my first question in this forum
That is typical Autodesk's behaviour in terms of programming help document since Autodesk adopted yearly product release in 2004 (Acad2005). They must think that they have "new" products every year and clients have to go with "new" products so busily that they would not have time to study the document, or if they do, when they go through the document, it is time for moving to next version.
It is particular bad on the general AutoCAD .NET API documentation. Howeever, if you see the AutoCAD Map programming API documentation, it is even worse: it is still referring to Visual Studio 2005, and some API assemly names only available in Acad2007/8 and have been renamed since...
Documentation always seems to be lowest man on the project totem pole, regardless of industry or project. Project managers want to spend the hours on "real" work, workers want to be doing the "real" work as well. At the end of the project, there's no budget left and nobody wants to do it.
Can any ADN members comment on whether the AcCoreMgd.dll references are up-to-date with this paid-access service, or are you in the same boat?
AcCoreMgd is mentioned in the ObjectARX SDK helpfiles - in the ObjectARX ReadMe->Release Notes. There (and the Migration guides in the helpfiles) is where we document changes to the SDK - both .NET and ObjectARX.
I've also notified our techpubs team about the outdated docs in the AutoCAD helpfiles. They tell me this was already reported as a bug. I'm sorry this happened - somehow that section of the AutoCAD help didn't get flagged as something our API techpubs team had to update.
BTW Why don't you consider Kean's blog posts to be a valid source of information? Kean is a member of the AutoCAD Architects team, and has a *very* popular blog (read by pretty much every AutoCAD .NET developer out there). Because of that, he and I agreed that he would post migration information on his blog this year rather than the ADN team running our usual migration webcast.
BTWBTW These videos may be helpful to anyone who wants to quickly see the 2013 migration basics for AutoCAD .NET and ObjectARX plug-ins - http://adndevblog.typepad.com/autocad/2012/04/migr
Thanks for the update.
I'd seen the references in the SDK and on Keans Blog and more recently on the new ADN DevBlog, but I noticed the omission from the Help files after I told someone to have a look at them to resolve Reference issues ... Embarrassing for me .
As I think you are aware, I believe that the help files should be complete and accessible without internet access ( but that's a discussion for another time ).
I have NO issue with Kean or his blog. In fact I'm quietly one of his ardent supporters. Without the information published there the development community would be still scratching it's collective head.
My comment was to stay anyone from pointing me to references I knew about and keep the focus on the Help Files.
I apologise for misspelling your name
Hello Every one,
I need a clarification very urgently...Please do me favour...
Currently we are using AutoCAD 2011 with Visual Studio 2008. I want to upgrade AutoCAD to AutoCAD 2013. Please let me know will AutoCAD 2013 supports Visual Studio 2008?
Thanks & Regards,
Prakash P V K
...Please let me know will AutoCAD 2013 supports Visual Studio 2008?...
NO. From ObjectARX 2013 Readme -> Release Notes:
Microsoft Visual Studio 2010 with Service Pack 1 should be used when compiling projects for use with AutoCAD 2013.