How to configure deployed MSI application to delete file without trigger self repair upon shortcut launch.
Hello, All.
Im modifying an application to delete a exisiting file and dropped new config file.
Since this was already deployed when I delete the file it will trigger self repair. How I'm going to suppress self repair when I delete the file?
Open for suggestions.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
vjaneczko
10 years ago
If you're creating a new MSI or creating a script to overwrite an existing file, you shouldn't have to worry. Self heal would only get started if the new file has an older timestamp or version number than what's in the original package. Since you'll most likely have a file that is the same or newer, it should be fine to drop the new file in place and not worry about it.
Comments:
-
Thank you for your answer, I should remove the file and dropped a new file. They are not same filename.
Eg.
File to remove Add.txt,
File to dropped Sub.txt.
Problem is Add.txt was a keypath in the deployed MSI and it will repair on application launch. - ajcbasilio 10 years ago-
If the app will no longer reference the "Add.txt" file, might as well just leave it on the hard drive. Nothing wrong with a little file sitting on a hard drive doing nothing, you know? Update the original MSI with the new "Sub.txt" file as the key path and you'll be all set for future deployments. - vjaneczko 10 years ago
-
Hmm do you have a way to update through MST that the Add.txt will remove and Sub.txt will deploy without removing the application? I must deploy a configuration only to tweak the deployed application.
Add.txt was seen in the application in GUI the request of customer this must remove. The only way is to delete but as I've said it was going to repair. - ajcbasilio 10 years ago
Posted by:
vjaneczko
10 years ago
Posted by:
jagadeish
10 years ago