Testing your app in Autocad longbow


Download 327.61 Kb.
NameTesting your app in Autocad longbow
page1/3
A typeTest
  1   2   3
AutoCAD Longbow

Porting your code to Visual Studio 2012

There’s not that much work needed to port your apps to AutoCAD Longbow, unless you are using acedCommand or acedCmd in which case you should be sure to read the section below More AutoCAD Longbow Porting Tips and also check out the AsyncCommandDemo_Src.zip sample code.



The basic porting instructions are as follows.

  1. Install Visual Studio 2012 and make sure you are running the latest Update

  2. Load your Solution/Project into Visual Studio 2012

    1. Accept all default conversion options

      1. Updates VC++ Compiler and Libraries to use V110

  3. If you are not using the ObjectARX Visual Studio project defaults (*.props), then update all libraries with version number suffixes to *20.lib

    1. acui20.lib

    2. adui20.lib

    3. acbr20.lib

    4. acgex20.lib

    5. ac1st20.lib

    6. acdb20.lib

    7. acge20.lib

    8. acISMobj20.lib

  4. Compile your application, possible errors and solutions are as follows



  • _WIN32_WINNT not defined. Defaulting to _WIN32_WINNT_MAXVER

    • Solution: #include in your stdafx.h at the top

  1. Load your application for testing

Testing your app in AutoCAD Longbow

For AutoCAD Longbow, be sure to test your applications under these scenarios

  1. Open, Save, Quit and then Open, Save, Quit!

    1. Open older DWG files in AutoCAD Longbow, make changes and save. Re-open and make sure your data is persisted correctly

    2. Open brand new DWG files in AutoCAD Longbow, make changes and save. Re-open and make sure your data is persisted correctly

    3. Run Audit before and after all Open, Save, Quit operations to verify integrity

  2. Pay particular attention to anywhere you use acedCommand or acedCmd

    1. You will get compiler errors when porting

    2. Refer to More AutoCAD Longbow Porting Tips below for more information.

  3. Document switching

    1. Make sure your Modeless dialogs work when the Welcome Dialog is displayed

    2. Make sure your Modeless dialogs work when in zero document state

  4. Any crashes, be sure to enter your email address into the crash error report dialog, along with any pertinent information. This is not only useful for us, but for you, it allows us to reference your crash dumps in case we need to help you with anything.

Porting your code to build with the Debug build of AutoCAD

Porting your code to build in Full Debug mode is fairly straight forward, but can get tricky depending on how big your project is and/or how unified the setup is across projects.

The process is purely about setting up your solution to link with the debug versions of Microsoft’s libraries and AutoCAD’s. Mixing Debug and Release libraries will cause random crashing when loaded and is not correctly setup, it is typically recognizable at compile time by a link warning similar to this:

already defined in MSVCRT.lib

Or

already defined in MSVCRTD.lib

  1. Load your project into Visual Studio 2012

  2. Create a new Build Configuration, derived from your Debug configuration called Full Debug

  3. In the Full Debug configuration Properties

    1. Verify that _DEBUG is defined

    2. Change project setting C/C++->Code Generation->Runtime Library = Multi-threaded debug DLL

    3. Add Preprocessor symbol AC_FULL_DEBUG

    4. If you are not using arxheaders.h (which automatically #pragma comment (lib)’s the AutoCAD libs) then update all libraries with version number suffixes from *20.lib to *20d.lib

      1. acui20d.lib

      2. adui20d.lib

      3. acbr20d.lib

      4. acgex20d.lib

      5. ac1st20d.lib

      6. acdb20d.lib

      7. acge20d.lib

      8. acISMobj20d.lib

  4. In Visual Studio Tools->Options->Debugging->Symbols

    1. Add a path to http://symbols.autodesk.com/symbols to allow you to get call-stack information

  5. Now compile your application, if you receive no link warnings such as the one above then you can try to load into the Debug build of AutoCAD using the Debugger

    1. If your App crashes AutoCAD on load

      1. Use depends.exe to make sure you are not linking with any Release MFC, CRT or AutoCAD libs

      2. Use Visual Studio Debugger to step through to see where it is crashing – it’s full debug remember!

      3. Use gflags.exe to enable loader snaps for acad.exe – watch the Output window in Visual Studio to see where the DLL load issue/crash is happening and why

    2. If you are doing Mixed Mode debugging, we recommend you use the 32bit version of the Debug build of AutoCAD as it works better with 32bit Visual Studio.


  1   2   3

Share in:

Related:

Testing your app in Autocad longbow iconSigning app Note: signing the app is only necessary when you intend...

Testing your app in Autocad longbow iconTesting Environment : Load & Performance Testing, Automation Testing, Manual Testing

Testing your app in Autocad longbow iconDownload the app To get started, make sure you are using an iPhone...

Testing your app in Autocad longbow iconConquests of the longbow: robin hood

Testing your app in Autocad longbow iconDescription of Product: Outlook Mobile app for ios is the business-class...

Testing your app in Autocad longbow iconBlind Square is a combination Point of Interest poi and basic navigating...

Testing your app in Autocad longbow iconIs the app name that appears to users. For this project, use "My First App."

Testing your app in Autocad longbow iconWalkthrough: Deploying a SignalR autohosted App to Office 365 Written...

Testing your app in Autocad longbow iconClaroCom is an ios app designed for aac (Augmentative and Alternative...

Testing your app in Autocad longbow iconAutocad rendering Basics




forms and shapes


When copying material provide a link © 2017
contacts
filling-form.info
search