Thanks for the nice videos on this site! I have learned alot!

One advice I found very interesting was to put the User Settings in a own Feature (from the Best Practices video), to make the self repair not take as much time. Great, I thought!

But I don't get it to work....
When I have the component in the Main feature, it does self repair but when I put it in it's own feature it installs for the installation runner, but it will not repair for "new" users.

I have tried to set exactly the same settings for both features, but it does not help.
Anyone got any ideas?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Has not anyone watched those movies???

Not even heard of the way to put current user-settings in a own component to minimize the repair-time??

Answered 05/24/2006 by: jonasm
Blue Belt

Please log in to comment
Seems that you're missing a repair trigger (component keypath) in the top feature.
When the user runs the application it will have a access a registry entry in a component under you're top feature to trigger the self-healing/repair.
Answered 05/24/2006 by: AngelD
Red Belt

Please log in to comment