Autodesk Inventor

[#1]

Has anyone been able to set up their debugging environment for 2012 Inventor AddIns? I have folllowed instructions from the 2012 Inventor SDK and the AddIn is correctly used by the app. However I keep getting messages about invalid or nonexistent debugging info and my breakpoints are never hit. Where should the .pdb file for the addin be placed?

[#2]

Hi,

In general, you should make sure that the pdb is in the same folder with the module. Please check the path of the addin module in your manifest file(.addin). If it is relative path, you should put the pdb to Inventor bin folder. If it is absolute path, you should put the pdb to the folder of the module.

Thanks,

Marshal

[#3]

I'm having an issue with debugging as well. I created a DLL for a dialog box for Inventor 2012. I have debug open an external program when debug begins. As soon as Inventor opens up, after the splash screen, I get a "DisconnectedContext was detected" error. Any help would be greatly appreciated.

[#4]

Hi,

The error is telling you that you have a pointer to a COM object that went away. It may be an issue in your codes. Please check.

Thanks,

Marshal

[#5]

I started a Class Library from scratch. 1. I imported the Autodesk Inventor Object Library into my references. 2. Set the Debugger to open Inventor 2012 on run. 3. Set the Target Framework to 3.5 I continue to get the DisconnectedContext error. I don't have an issue with this working with Inventor 2011. Is there something I may be missing that needs to be added/changed for Inventor 2012?

[#6]

I commented out all of my code and started the debug process. I recieved the same error. I know my code is not the problem. Is this an issue with Inventor 2012?

[#7]

You will probably get more responses in the Inventor Customization forum.

[#8 · Accepted solution]

The loading Mechanism has slightly changed in inventor 2012

Run wizards.exe in SDk Folder

a template will be added to ur VS 2010

to load an addin

copy the dll file to

\programdata\Autodesk \inventor 2012\addins

and copy the manifest(.addin)  to the same directory

this should work

[#9]

This is actually for a dll that is being triggered through iLogic.

[#10]

A coworker of mine is having the same issue running completely different code. We are trying to debug Inventor 2012 64-bit with Visual Studios 2010 Professional. We are setting up our assemblies to fire a DLL to perform some automation. We can manually attach Visual Studio to the Inventor process and debug works fine. However, this is an inconvenient/unnecessary step when trying to debug.