Andreas Isler
12-23-2005, 05:30 AM
Adding files to a basic MSI project upgraded from DevStudio9 to IS11.5 may cause big problems.
Situation:
File keys in DevStudio9 are set as upper- and lower-case. In IS11.5 they are set just as lower-case.
Example:
See attached KexFile.ism. It is made with DevStudio9 and contains a component TASKMAN.EXE with the file key TASKMAN.EXE.
Import it into IS11.5, start the component wizard and just add the file C:\Windows\TASKMAN.EXE. This will make a new component TASKMAN.EXE1 with the file key taskman.exe. Compile it.
Error:
Compilation runs into error 6636. The solution suggested is to change identical file keys in the direct editor. As we have hundreds of potentionally affected files not a solution at all!
The error occurs when files are compressed.
Suggestions:
- IS11.5 should consider file keys with upper- and lower case when it gives a new file key (easy to implement for an IS developer)
- Is there a setting for IS11.5 that corrects this error?
If not, customers must do the following:
- Change all file keys to lower-case after updating. (But: which tables are affected and which are not?)
- Remove all files of all affected components and add them again. (A lot of stupid work)
A solution would be an appreciated Christmas gift. ;)
Situation:
File keys in DevStudio9 are set as upper- and lower-case. In IS11.5 they are set just as lower-case.
Example:
See attached KexFile.ism. It is made with DevStudio9 and contains a component TASKMAN.EXE with the file key TASKMAN.EXE.
Import it into IS11.5, start the component wizard and just add the file C:\Windows\TASKMAN.EXE. This will make a new component TASKMAN.EXE1 with the file key taskman.exe. Compile it.
Error:
Compilation runs into error 6636. The solution suggested is to change identical file keys in the direct editor. As we have hundreds of potentionally affected files not a solution at all!
The error occurs when files are compressed.
Suggestions:
- IS11.5 should consider file keys with upper- and lower case when it gives a new file key (easy to implement for an IS developer)
- Is there a setting for IS11.5 that corrects this error?
If not, customers must do the following:
- Change all file keys to lower-case after updating. (But: which tables are affected and which are not?)
- Remove all files of all affected components and add them again. (A lot of stupid work)
A solution would be an appreciated Christmas gift. ;)