Adding files, new cab and patches
Hi all,
From a vendor MSI package, which already includes a cab file, i created a MST that add some files to very specific folders. My files are added to a new cabinet file. When i install this new package, my files are correctly copied at the desired location and self healing is working as expected.
The problem is, when i apply the vendor MSP files to my package, the self healing does not work anymore because it is looking for my files inside the original vendor cab instead of my new cab file.
Are the MSP files messing with the original files attributes or something?
Before installing the MSP, selfhealing finds my files under my new cab files, after, they search in the original cab file, omitting the new one.
Did anybody had this problems before?
Thanks
From a vendor MSI package, which already includes a cab file, i created a MST that add some files to very specific folders. My files are added to a new cabinet file. When i install this new package, my files are correctly copied at the desired location and self healing is working as expected.
The problem is, when i apply the vendor MSP files to my package, the self healing does not work anymore because it is looking for my files inside the original vendor cab instead of my new cab file.
Are the MSP files messing with the original files attributes or something?
Before installing the MSP, selfhealing finds my files under my new cab files, after, they search in the original cab file, omitting the new one.
Did anybody had this problems before?
Thanks
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
michaelnowell
15 years ago
You'll find this much easier if you where to create an admin installation of your MSI, apply your patch and add your files into your transform.
By creating an admin installtion you will eliminate the need for external cab files as your additional files will just be sitting in the folder structure generated by the admin install (or you may have to create additional folders if your files are in folders not specified during the admin install).
By creating an admin installtion you will eliminate the need for external cab files as your additional files will just be sitting in the folder structure generated by the admin install (or you may have to create additional folders if your files are in folders not specified during the admin install).
Posted by:
PackagerWannaBe
15 years ago
have to create additional folders if your files are in folders not specified during the admin install).
Thanks for suggesting. If i understand correctly, this admin install option will get rid of the cab files completely. As per our distribution scenario, we need to create packages that are easily transportable (msi with or without cab files).
Any other suggestions?
Thanks
Posted by:
PackagerWannaBe
15 years ago
Hi,
I solved the problem.
I changed the file sequence attribute so far now it's working. From 3490 to 20000.
Thanks for the suggestion.
I solved the problem.
I changed the file sequence attribute so far now it's working. From 3490 to 20000.
Thanks for the suggestion.
Posted by:
PackagerWannaBe
15 years ago
Hi again,
Just so i can understand better about admin install. What are the real advantage of admin install? Is it just a way to save space on users's machines or is there other advantages?
Thks
Just so i can understand better about admin install. What are the real advantage of admin install? Is it just a way to save space on users's machines or is there other advantages?
Thks
Posted by:
michaelnowell
15 years ago
One of the main advantages of using an admin install is that you can directly apply vendor patches to it. By doing so, you can then run a REINSTALL=ALL (with REINSTALLMODE=xxxxx, where xxxxx is your desired reinstall options) on all of you clients that have the software installed and this will update them with the changes made in the patch. Any new installs from this admin point will get the patched install from the start.
This theory also works when you update any specific files within you admin install. E.g. you need to update a .mdb/pdf/dll
You'll find that on the odd occasion where you need do this, it will save you a lot of time.
This theory also works when you update any specific files within you admin install. E.g. you need to update a .mdb/pdf/dll
You'll find that on the odd occasion where you need do this, it will save you a lot of time.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.