Updating GUI interface and Add-In - how to properly change add in version.

Updating GUI interface and Add-In - how to properly change add in version.

Anonymous
Not applicable
774 Views
1 Reply
Message 1 of 2

Updating GUI interface and Add-In - how to properly change add in version.

Anonymous
Not applicable

Hi all,

 

As a part of a project i am currently fiddling around with the creation of an inventor plugin written i C++. I have successfully installed the SDK, along with the VC++ samples. I have also installed the VIsual Studio Templates for a quick Add-In "skeleton" to start with. 

 

Now, by looking through the documentation and the samples i have written some definitions for a new button and a new panel. At this point i have two problems:

 

  1. The Add-In only compiles in Debug mode, while in the release mode it cannot finde the files in the "include" directory of the SDK, even though i have specifically pointed to the folder in the project options.
  2. When i compile the Add-In successfully in debug mode and launch Inventor I can see that my Add-In has been loaded, but the GUI is not visible in the Ribbon interface. As far as i have understood this has something to do with the "firsttime" boolean, which is only true when the Add In is loaded the first time. I have searched in the discussion groups, and read a multiple of times that i should change the version og the Add-In to update the Ribbon interface. I have tried seaching in the registry for the CLSID and the Add-In Name and changed every single value that is named something with version but with no luck.  In addition I've tried to change the CLSID, unregistering and re-registering the Add-In, as well as changing a version variable in the code. On a final note, i have tried changing a button text in an existing and working sample addin, but i can't see this change in Inventor either.
Sorry about the long question, but i have really tried a lot of strategies to get it working. 
My setup is as follows:
Autodesk Inventor 2011 x64
Visual Studio 2008
Windows 7 x64.
Hope someone has a hunch as to what could be my problem? I am convinced that it is just a small glitch in my understanding of how to do this (i am not an experienced C++ developer)
Thanks!

 

0 Likes
775 Views
1 Reply
Reply (1)
Message 2 of 2

Anonymous
Not applicable

The problem has been solved. It turned out that the "register for COM interop" function didn't work for my x64 based system. Instead i added a custom regasm command as post-build event. Also, here it is important to remember to choose the regasm in the %windir%/Microsoft.net/framwork64 directory, or else it won't work!

0 Likes