Inventor Add-in Templates for 2015

[Anonymous]

We are rolling into 2015 from 2012 which means that our onsave VBA modules no longer functions. I've replaced all of that code with functioning iLogic code (so easy!) but like and now I need to get the external iLogic (with triggers) into our pre-2015 data on an "as-used" basis.

I downloaded and tried Jürgen's solution with decent results but it needs to be tailored for site-wide distribution so I've decided to generate an add-in that meets our needs, my first add-in BTW!

Link to Jürgen's solution -

http://inventortrenches.blogspot.com/2011/08/built-for-speed-running-ilogic-rules.html

I've read thru all of the plug-in tutorials that I can find and they all point to the same method of template extraction but none of those methods seem to work in 2015 since the .zip files don't exist for pasting into the correct folders. From what I understand, simply deploying the .msi's should do the trick but it doesn't. Using the 2014 .zips in the correct locations kind of works although the 2012 templates seem to work better. I also caught some chatter about a .NET installation but that didn't make any sense to me.

I'm running a new install of Inv 2015 Pro 64bit and Desktop Express 2013, can anyone point me to a walkthrough that details the 2015 template extraction method?

Thanks!

Eric

[mr_ensing]

Today (almost 2 years later) your extract command wouldn't work for me. A bit of google-fu learned i had to change 1 letter:

msiexec /a C:\Developertools\developertools.msi /qb TARGETDIR=C:\Developertools\DT

Maybe this is of some use for somebody finding this page through google.

[Anonymous]

i have installed autodesk inventor pro 2015 student version, i want to install developer tools. when i tried doing that it is throwing an error saying that it could not find any version of microsoft visual studio although i have installed microsoft visual studio 2015 community version. please can anyone help me to solve this issue.

---

[Anonymous]

I see this is an old post...

since this manifest part in the postbuild never worked for me, I always delete it... Didn't have any issues doing so... Anyway, what is this good/needed for...? Maybe I miss some basic understanding here... However I can live without....

BR,

Daniel

[Anonymous]

Hi, not sure but I think devTools 2015 doesn't recognize VS2015, should work with VS2013-... You may use the Workaround described in the accepted solution to work with VS2015 (be aware of the right .net Framework Version in your Addin as well!)

BR,

Daniel

[YuhanZhang]

The PostEvent will 1) add the .manifest to the binary, this is needed for reg-free mechanism that Microsoft supports. 2) Copy the binary and .addin to a proper folder so Inventor can find the addin.

Does it raise an error when you say the PostEvent does not work? Can you provide any more info about it?

[YuhanZhang]

After you installing the VS2015 or other VS versions, you should launch it once to configure it, then VS will create some more default paths for templates, wizards etc., then the Inventor Addin Wizards can find the path and install our Inventor Addin wizard to proper folder. Also please check the SDK_Readme.htm which is located in the same folder as DeveloperTools.msi to know if the Inventor Addin wizard can work for VS2015 or not.

[Anonymous]

Hi Rocky,

I'm facing this problem all over the time, VS is installed and already used, but launching DEvtools-Installer does not include the templates, althought it sais, Installation were succeeded.

Currently I had this with VS2017 Pro + DevTools 2018.... I needed to put the templates manually in the "Usertemplates" of VS (Appdata.....) in order to get them recognized by VS...

However, until this workaround works, I'm happy 🙂

BR,

Daniel

[Anonymous]

I'm not sure the manifest-thing is really needed.....

However, the buld fails on Postbuild at the call of mt... It may be some missing Sysvar (for getting VS-Path, whatever), as long as the addin works, I don't really invent effort to investigate further 🙂

I always delete this Lines and keep (adapt them as needed) the xcopy-ones.

Never had an issue running my  addins, w/o manually register them in the reg.... 

I guess, inventor does it for me (can remember to see them somewhere in the reg...)

[kmiller]

Not sure if it matters or helps at all at this point.  But I need to launch my vs to run as admin for some of my older programs to call the mt file on postbuild.

I also have had the same issue with the VS templates with 2016 sdk in having to copy them to vs location.  Still working on 2018 sdk installation.

[YuhanZhang]

The Inventor Addin Wizard template does not support VS2017 in Inventor 2018 and previous SDKs, we will support it in Inventor 2019 SDK. Yes, currently you can manually copy the templates and modify them for VS2017 as a workaround.

[Ahmed_204]

Thats really a good solution , I used the same for autocad dotnet wizard and it worked for me just fine 

@wmgshurik  thanks