Software Deployment

ICE 38 has two different types of errors.. depending on Current user key path or registry not found.

If its for current user key path, this is normally fixed inorder to get your current user files and registries installed during the first launch in any user.

HTH

Thanks,
but I'm not sure I understand. I get user files installed even if I don't fix this

hi Nicklas,
ice38 ensures that all users files gets installed/repaired especially for machines with multiple users.. this makes sense if your application is being used by multiple users on a single machine as it ensures that all necessary user files are present on their profile

regards
rick

Thanks Rick,
but why do you have to use the registry as key path, why can't you use a file in the user's folder?

Hi Nicklas

but why do you have to use the registry as key path, why can't you use a file in the user's folder?

Using a file in the users folder as a keypath is not advised as the user will have rights to delete it - if they do it would cause a repair when the user really does want rid of that file..

Using a HKCU reg key means users won't be easilly able to remove the keypath causing a repair - but if the keypath doesn't exist to start with the MSI (say for advertising purposes) will repair and write the current user file/s installed by that component.

Hope that makes sense, it did when I typed it [;)]

It's standard MSI validation rules - more info here.

Cheers,
Rob.

Thanks,
I have a slightly different view on this. I thought key paths where used for "required" files/registry keys. If the key path is broken (e.g. the file is missing) then the msi will repair the application making it work again. If the file is not "required" and the application works fine without it, I don't see a point in setting it as key path. If I have a "required" user file and the file is deleted for some reason, how would I get it back if my key path is a registry key that is ok?

hi..
setting a file in current user profile as a keypath can trigger unwanted activity in the installer (auto repair on every launch) if the file is modified or removed on purpose by the user..

regards
rick

Hi,
I have never seen msi repair an application because of a modified file, I tested, but could not force a repair by modifying files (maybe i didn't do it right).
How can the repair be unwanted if the file is required by the application to run?
Or are you telling me that "required" files should never be placed in user only folders?

Thanks again.

Nicklas,
As far as I know I dont believe you can trigger an msi to repair if the file contents are changed..[:D]. MSI does refers only to the file/registry (present or not) if its the key path. Have I understood you correctly?

I would be happy to know if we have this option in MSI...[8D]

Yes,
msi only checks if a file/registry key is missing.
[&o]

my bad [&:] that should have been "REMOVED" only.. come to think of it.. can msi's check if a file is modified (by date and time stamp for file that has no versions) and trigger a repair?

regards
rick

Do whatever you like to the file, as long as you have a registry key as key path nothing will happen.

Thanks everyone for the feedback.
I'm just going to ignore ICE38 and ICE43, I don't see any point in fixing them.