Ok moved to another company and they have an odd requirement that any custom/added files should be stored uncompressed with the msi (when creating a transform) instead of a cab.

Reason is, they can change custom files on the fly... Ok some possible issues with repairs/version/hash etc but it seems to work for them (don't really know, haven't ever tried to do this before)...

Ok so my question... Some MSI I can leave the custom file in the same dir as the msi (source root?) and it installs ok... while others I have to have some form of the folder structure there aka Application Data\APP1\file1.

Not a huge deal but I was trying to figure out how to setup all my MSTs to use the SourceDir for custom files instead of having 3 level folder structures for 1 small file (in with the MSI)...


I figure it has something to do with the . and : in the the directory table and changing the source directory. I haven't had much luck figuring it out.

I have tried editing the final "DefaultDir" column in the directory table like "FOLDER:" and ":FOLDER", "FOLDER:SourceDir" but get path too long errors or can't find file in PATH...\SourceDir\FILE when installing.

Granted I have been tacking on needed folders to the vendor created structure in the directory table. usually only 1 or 2 levels... I assume if I wanted to truly change the source to root I may have to recreate the whole path in the dir table? Otherwise I would screw up the source for the other vendor files being installed in parent directories...

Anyone have insight?
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


You'll get it with time, until then ;)
Answered 04/08/2011 by: AngelD
Red Belt

Please log in to comment
Thanks for the reading... will have to toy around with it a bit!
Answered 04/10/2011 by: dandirk
Third Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity