Hi All!

Newbie to the world of ITNinja, this is my first post!

Having a bit of an issue with SketchUp Pro Version 8.

I have made all the neccessary ammendments inside the registry (HKCU), supressed all dialog boxes and windows, and placed a few files inside [AppDataFolder], advertised the shortcuts as they are not advertised by default and so on and so forth.

I come to test the application, and for some reason it isnt applying anything that i have changed on User, and it doesnt self-heal, so the dialog boxes keep coming up and things.

I would use active setup, but because i already have advertised shortcuts, i dont think that is the best route to go down.

Does anyone have any ideas on what steps to take in order to get this application fully working on user, and to make all the neccessary things above, apply!?

This is an MSI with a Transform.

Any Help is appreciated!



Answer Summary:
2 Comments   [ + ] Show Comments


  • Hi VBScab / Badger :)

    Managed to get this working fine, and got it released today!

    Thank-you for your help!
  • coolio, thanks for the update
Please log in to comment



you do have to dance a bit with this one. I did sketch up 8 (not pro)
For that one, when you advertise the shortcuts (to initiate the repair) I used the feature, SketchUpModule and attached my new component with the HKCU keys to that.

I would suggest making sure you have unique keypaths sets for your HKCU reg keys (and a reg key as the key path for the files in AppData). Then ensure you hierarchy is setup properly so everything is in the correct Features. (and yes, stay away from the ActiveSetup)

Answered 12/19/2014 by: Badger
Red Belt

Please log in to comment
To correctly trigger self-healing with an advertised entry-point, you need to:

- create a new, top-level feature to contain the user-level components.
- add a key path using a registry key, not a file. If there's no registry data as part of the app, make some up. I use 'Software\[My_client's_name]\Installed Applications\[ProductCode]' with a value 'Installed', populated with data '[ProductCode]'. Remember that if your package is installing user-level files and your authoring tool creates separate components for every folder, you'll need a key path for each of those components. Otherwise, self-healing will try to repair the installing user's folder structure, as the WI engine regards a folder/file component with no key path set as the default key path (if you catch my drift). Alternatively, move all the folder-creation into the same component as the registry data.
- make the feature containing the advertised entry-point a child of this new feature.
Answered 12/19/2014 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity