Autocad ARX 2018 accore.dll exception

Autocad ARX 2018 accore.dll exception

phenriet
Enthusiast Enthusiast
3,256 Views
4 Replies
Message 1 of 5

Autocad ARX 2018 accore.dll exception

phenriet
Enthusiast
Enthusiast

Hye,

 

I need your help today because I'm migrating my application from 2017 to 2018 and get an exception after Autocad closed.

My app is composed of C program which generates an ARX and C# DLLs wrapped with it.

 

The exception comes from accore.dll which is an autocad DLL. I have no more informations and no code line gives any exception.

 

My arx is loaded well and anything works but I get the accorde.dll exception when I quit Autocad. Autocad quits well if I launch it alone.

 

Have you an idea?

 

Thanks and sorry for my french english!

0 Likes
3,257 Views
4 Replies
Replies (4)
Message 2 of 5

tbrammer
Advisor
Advisor

Are you using Visual Studio 2015 Update 3?

 

Did you follow the steps described in the Migration Guide? :

  • Reference the latest versions of the libraries used by the application
  • Change code statements of modified or obsolete methods used in an application
  • Recompile the application

Did you use the right property sheet files (*.props) in your 2018 configuration?

Bring up the Property Manager with [View]->[Other Windows]->[Property Manager], expand your configuration and look for ObjectARX entries:

PropManWindow.jpg

If your project uses a 2017 props file replace it with a 2018 props file in your configuration.

Do you use  #pragma comment (lib,"mylib.lib")  statements to include libraries? Check if you include the right versions.

 

If your migration is OK and you still have problems I would recomment to remove parts of your code to find out what causes the crash.

Try to simplify as much as possible until the crash vanishes. Than find out when it appears again.

Does it also crash if there is only an empty drawing opened and no commands have been issued?

 

Do you use reactors? I.e. AcEditorReactor? Try to run your app without your reactors.


Thomas Brammer ● Software Developer ● imos AGLinkedIn
If an answer solves your problem please [ACCEPT SOLUTION]. Otherwise explain why not.

0 Likes
Message 3 of 5

Alexander.Rivilis
Mentor
Mentor

1. You have to check your code in kUnloadAppMsg handler.

2. You have to check reactors.

3. It is possible your app destroy acad.exe memory.

4. etc...

 

Відповідь корисна? Клікніть на "ВПОДОБАЙКУ" цім повідомленням! | Do you find the posts helpful? "LIKE" these posts!
Находите сообщения полезными? Поставьте "НРАВИТСЯ" этим сообщениям!
На ваше запитання відповіли? Натисніть кнопку "ПРИЙНЯТИ РІШЕННЯ" | Have your question been answered successfully? Click "ACCEPT SOLUTION" button.
На ваш вопрос успешно ответили? Нажмите кнопку "УТВЕРДИТЬ РЕШЕНИЕ"


Alexander Rivilis / Александр Ривилис / Олександр Рівіліс
Programmer & Teacher & Helper / Программист - Учитель - Помощник / Програміст - вчитель - помічник
Facebook | Twitter | LinkedIn
Expert Elite Member

0 Likes
Message 4 of 5

phenriet
Enthusiast
Enthusiast

Hye, 

 

Thank you for your response, 

 

I'm using visual studio 2015 update 3 and I changed all my libraries references.

 

It's important to know that it's a 15 year application, so all the project was not done by me but you can see in screenshots joined that ObjectARX references are done in link editor.

 

I have already watch migration guide and deprecated functions, all my code is compiled well and my arx 2018 is well loaded. There is no more references to 2017 in all the solution.

 

About function migration, do you think that a deprecated function could be compiled and launched in ARX 2018?

 

About the .props, we never had any props file in our application. All the configuration is done in vcxproj.

 

So I think that the solution can be to comment code but I have already use the debug and run in the code. I can find the last line of my code and get no exception. The exception comes after the last line of my code (after Autocad window is already closed).

 

Finally we don't use #pragma statements to include libraries

 

Thank you for your help.

 

Sorry for my french english!

 

Pierre.

 

 

 

0 Likes
Message 5 of 5

phenriet
Enthusiast
Enthusiast

I think that the problem comes after the call of the function: CallWindowProc from WinUser.h. 

but the exception comes from accore.dll...

I don't understand what happen...

0 Likes