- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Yes it sounds like you’ve got extra steps you don’t require.
Why should they need to edit the application project?
Just upload the new application project, have them pull it down and point their app options to that location.
deploying the usercustomization file along with it (so they get two files) handles the buttons you’ve created if any.
They do not need to copy paste modules.
Personally I’d ditch the Vault and stick both files on a share. The permissions aren’t so much to prevent users editing (you can password protect the project in the IDE), it’s to make sure you can overwrite it.
That way your works instruction has a one time path change in App Options and an occasional reimport of usercustomization.xml each time you add a new button (not all macros require buttons).
I have literally dozens of macros, modules, forms, classes all in a single default.ivb. Users never edit the ivb.
Sure it takes a wee minute to wrap your head round it buts it’s way easier than your describing.
Did you find this reply helpful ? If so please use the Accept as Solution or Kudos button below.
---------------------------------------------------------------------------------------------------------------------------
Inventor 2010 Certified Professional
Currently using 2023 Pro