topic Switch from Windows 7 AutoCAD 2014 to Windows 10 AutoCAD 2018 in .NET Forum

Switch from Windows 7 AutoCAD 2014 to Windows 10 AutoCAD 2018

Anonymous — Wed, 24 Oct 2018 09:35:47 GMT

I have DLL modules that works fine in current environment (Windows 7 and AutoCAD 2014). I distribute recently same DLL to my colleague who has Windows 10 and AutoCAD 2018. NETLOAD loads DLL without error, custom function is visible but when he tried to run this custom code AutoCAD crashes without any warning message.

Have you notice similiar issues?

Is there something in code that I have to consider related to switch to Windows 10 or/and AutoCAD 2018?

Re: Switch from Windows 7 AutoCAD 2014 to Windows 10 AutoCAD 2018

Alfred.NESWADBA — Wed, 24 Oct 2018 10:57:44 GMT

Hi,

AutoCAD 2014 and AutoCAD 2018 are not fully API compatible, depending on which parts of API functions are used could result in crashes.

The vendor of that code has to port and test his app to the new AutoCAD release.

- alfred -

Re: Switch from Windows 7 AutoCAD 2014 to Windows 10 AutoCAD 2018

_gile — Wed, 24 Oct 2018 11:04:25 GMT

Hi,

If your code references the AutoCAD Interop libraries (COM API), you should compile a version which references the 2018 Interop libraries.

If your code P/Invoke unmanaged methods you have to look if the EntryCode didn't change.

If your code only uses the .NET API managed methods ("pure .NET") it should work, anyway, you can try to build and debug a new version with the same code but targeting the .NET Framework 4.6 and referencing the 2018 AutoCAD .NET libraries.

Re: Switch from Windows 7 AutoCAD 2014 to Windows 10 AutoCAD 2018

Alfred.NESWADBA — Wed, 24 Oct 2018 11:07:55 GMT

Just to also add ... if using SendCommand (or any type of sending a string to the commandline) changed because of fibers changed in AutoCAD 2015.

- alfred -

Re: Switch from Windows 7 AutoCAD 2014 to Windows 10 AutoCAD 2018

Anonymous — Wed, 24 Oct 2018 11:19:07 GMT

What you mean by "fibers changed" ?

I am using send command:

private void SendStringToExecute(string sToExecute) {
    //Cancel running commands
    if(Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.CommandInProgress != "" && Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.CommandInProgress != "CD") {
        AcadDocument oDoc = (AcadDocument)Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.GetAcadDocument();
        oDoc.SendCommand("\x03\x03");
    }
    Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.SendStringToExecute(sToExecute.Replace(" ", "\n"), false, false, false);
}

Do you have / can you provide example of new solution?

Re: Switch from Windows 7 AutoCAD 2014 to Windows 10 AutoCAD 2018

Alfred.NESWADBA — Wed, 24 Oct 2018 11:22:36 GMT

Hi,

>> can you provide example of new solution?

There are some blogs out describing more detailed what changed and how to manage that, e.g. >>>this<<< or >>>that<<<

- alfred -