/build/static/layout/Breadcrumb_cap_w.png

Repair component with only user settings...

Hi!

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?

/Jonas

0 Comments   [ + ] Show comments

Answers (2)

Posted by: jonasm 18 years ago
Blue Belt
0
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??

/Jonas
Posted by: AngelD 18 years ago
Red Belt
0
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ