Sending Add-Ins to other users

Sending Add-Ins to other users

Anonymous
Not applicable
1,169 Views
7 Replies
Message 1 of 8

Sending Add-Ins to other users

Anonymous
Not applicable

I have modified some Add-in code to create a iProperties dialog that creates custom iProperties for material and painting specs. I was wondering if anybody had any idea how I can roll this program out to other users within my engineering group. Disclaimer: I have zero IT experience and have learned just enough Visual Basic and Visual studio to modify the program. Currently the program works fine on my Inventor 2018. I am able to generate a .exe and .msi file  from VS 2019, but it still doesn't work for other users. Please help!!!!

0 Likes
1,170 Views
7 Replies
Replies (7)
Message 2 of 8

bradeneuropeArthur
Mentor
Mentor

I use a set up compiler for it and create an installer.

This exe can be run by the user.

 

inno setup compiler

 

Easy to use..

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

0 Likes
Message 3 of 8

jjstr8
Collaborator
Collaborator

What's not working?  Is the installer not putting your DLL in the right location?  I put my add-ins under C:\ProgramData, so I end up having to run a VB script to modify the msi file to add 'EnableUserControl=1' to allow writing to that location.

0 Likes
Message 4 of 8

bradeneuropeArthur
Mentor
Mentor

I think he is questioning about how to distribute it easily.

You could use a script. Bat file that copies the files everytime by placing this bat file in the startup folder from windows!

This could also be an option!

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

0 Likes
Message 5 of 8

alewer
Advocate
Advocate

To add to what other users have said:

 

When you build your addin, an .addin and .dll file are created. Another user can use the addin by placing a copy of these two files to a folder. Which folder you use depends on what user(s) and Inventor version(s) you want to have the addin. From the API help ("Creating an Inventor Add-In," section "Where to Put Your Files"):

  1. All Users, Version Independent
    Windows 7/8.1/10 - %ALLUSERSPROFILE%\Autodesk\Inventor Addins\
  2. All Users, Version Dependent
    Windows 7/8.1/10 - %ALLUSERSPROFILE%\Autodesk\Inventor 20xx\Addins\
  3. Per User, Version Dependent
    In Window 7/8.1/10 - %APPDATA%\Autodesk\Inventor 20xx\Addins\
  4. Per User, Version Independent
    In Window 7/8.1/10 - %APPDATA%\Autodesk\ApplicationPlugins

As other users said, you can automate these with a .bat file, by creating an installer, etc. But the basics are that those two files (.dll and .addin) need to be moved to one of these folders.

0 Likes
Message 6 of 8

jaypieper
Enthusiast
Enthusiast

I have attached a PDF file from Autodesk University. Near the end of the PDF Brian Ekins talks about generating a install file. He even links to a Installer program. I have not had the chance to try it but it seems to be well documented. Hopefully this helps.

Message 7 of 8

bradeneuropeArthur
Mentor
Mentor

For the Inno setup Compiler see this link.

 

https://www.jrsoftware.org/isinfo.php

 

And for the Both file:

@echo off
xcopy "COPY FROM PATH DLL" "C:\Program Files\Autodesk\Inventor 20##\Bin\" /y

xcopy "COPY FROM PATH ADDIN" "C:\ProgramData\Autodesk\Inventor 20##\Addins\" /y

 

Regards,

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

Message 8 of 8

jjstr8
Collaborator
Collaborator

@bradeneuropeArthur wrote:

I think he is questioning about how to distribute it easily.

You could use a script. Bat file that copies the files everytime by placing this bat file in the startup folder from windows!

This could also be an option!


I wasn't sure.  Sounded like a problem I had where the installer compiled correctly, but couldn't put the files in the designated folder on someone else's computer due to permissions.  I ended up running a VB script on the msi in my post-build event.