![]() |
#1
|
|||
|
|||
![]()
I faced this issue for long time so I'm sharing the solution I finally found
![]() Problem: CorelDraw include some protection probably to avoid reverse engineering and thus will crash if he detects a debugger is present. This makes it almost impossible to write C++ DLL or C# WPF. Solution: Use API Monitor v2 to launch CorelDRAW, ignore Unhandled exception dialogs and attach VisualStudio to CorelDraw ;-) Full process with picture below: 1) launch CorelDraw with API Monitor using RemoteThread (Extended): ![]() 2) Ignore the Exception dialogs, i.e. leave them open, don't click on any buttons, CorelDRAW will continue to launch normally ;-) ![]() 3) Attach VisualStudio to CorelDRAW process: ![]() 4) You can now fully debug your DLL/WPF, including seen variables, invoking Coreldraw object in watch window etc... ![]() ![]() Comment: this is for CorelDRAW X6 64 bits but I would guess similar trick should work with other versions Last edited by Plixo; 12-12-2013 at 05:19. Reason: highlight important points |
![]() |
Tags |
coreldrawx6, debug, dll, wpf |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
BeginCommandGroup while debugging macro | vjCorel | CorelDRAW/Corel DESIGNER VBA | 2 | 23-04-2009 14:17 |
multiple Debugging Errors | KriZa | General | 2 | 15-01-2008 14:27 |
Workspace X3 + Script Debugging? | Sunny | General | 1 | 09-06-2006 13:13 |
Debugging help required | Peter Clifton | CorelDRAW/Corel DESIGNER VBA | 2 | 03-03-2004 17:28 |