Mr Spot
2010-04-29, 03:14 AM
Hey,
Previously for a rollout I would create a deployment, then run a batch utility that I created to update the Revit.ini and KeyboardShortcuts.txt file. Then finally install any extensions.
With XML keyboard shortcut files I'm wondering if anyone has developed a more intuitive way to roll it out.
I'm imagining a script that:
Scans the Revit.ini file for particular lines to add and update rather than simply overwriting, thus not effecting any existing extensions installed.
Updates the xml keyboard shortcuts file that Revit users initially. Currently I have to wait til a user uses revit and then from within Revit select the xml file...Another cool ability would be to easily include extensions within a deployment... I guess this is probably possible if you know how to edit the msi?
Any ideas? If not, I might need to create an API to do this.
Previously for a rollout I would create a deployment, then run a batch utility that I created to update the Revit.ini and KeyboardShortcuts.txt file. Then finally install any extensions.
With XML keyboard shortcut files I'm wondering if anyone has developed a more intuitive way to roll it out.
I'm imagining a script that:
Scans the Revit.ini file for particular lines to add and update rather than simply overwriting, thus not effecting any existing extensions installed.
Updates the xml keyboard shortcuts file that Revit users initially. Currently I have to wait til a user uses revit and then from within Revit select the xml file...Another cool ability would be to easily include extensions within a deployment... I guess this is probably possible if you know how to edit the msi?
Any ideas? If not, I might need to create an API to do this.