Moving from 2010 to 2013

[Mark-k5xh]

I recently wrote a routine on AutoCad 2010. Tonight I downloaded a trial copy of 2013. The dll that I created in 2010 will not work in 2013. The NETLOAD command seems to execute without errors but when I type the new command I get an error that says the command can't be found.

The intended target for what I wrote is 2012 but I did not have that available for testing.

This is my first application that I have written that is required to run on a different version from what I have.

Can someone please tell me if this is normal? Must I develope my code on a system what has the intended target version? Or did I fail to do something when I installed 2013?

Thanks,

Mark

[Alfred.NESWADBA]

Hi,

>> Can someone please tell me if this is normal?

>> Must I develope my code on a system what has the intended target version?

It's normal, yes, as 2013 breaks the binary compatibility to 2012 (and before).

Take your project files, replace the referenced lib's to that of 2013 and compile your project. You'll need to make some changes, but that's the way you get it to work with 2013.

Good luck, - alfred -

[Alexander.Rivilis]

Migrating ObjectARX and .NET plug-ins to AutoCAD 2013

[Mark-k5xh]

Thanks!

I found that I needed to add an additional reference to the list. I started a new project using 2013 and copied all the source code over. After adding the new ref it all worked.

Mark

[chiefbraincloud]

Just to be clear, the app you developed for 2010 would have worked in 2012 (barring a couple of minor signature changes), but if you have updated it to 2013 it will NOT work with 2012.  If your target deployment is for 2012, you'll want to go back to your original app, and either test it on a 2012 installation to see if you have used any of the few methods that changed, or obtain a 2012 license to test and debug for 2012. 

The new release of 2013 AutoCAD is the most major API change since the 2006-2007 split.