Hey, have been browsing the site for a while, but havent found anything on this topic. Its not exactly a problem, but more of an annoyance. Recently more and more vendor msi files come with everything under the "files" section placed directly under "Destination Computer", and not in the normal file structure when looking at the package in Package Studio.

Can anyone explain why this is done? Is there a reason for this?
0 Comments   [ + ] Show Comments

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.

Answers

0
more and more vendor msi files come with everything under the "files" section placed directly under "Destination Computer"
This is used (not that often) when who ever made the package is using a Set Directory custom action to "direct" the directory structure outside of the regular Directory table entries. Mostly used when files/directories are to be installed in the root of a drive.

Can't say I've seen much of this, could you specify some examples of packages you've seen this in?
Answered 05/27/2008 by: AngelD
Red Belt

Please log in to comment
0
i found apps build by Visual Studios do this.

no or one entry in the directory table, just a set directory to move to required location.

the packager build into VS is complete rubbish.
Answered 05/27/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Thanks John!
Answered 05/28/2008 by: AngelD
Red Belt

Please log in to comment
0
Thanks for the answers! Most of the packages are probably unheard of by most of you, most of them created by small vendors.. Anyways, ill poke around a bit more, and see if they use the built in packager in VS, and see if they are willing to look it over again..
Answered 05/29/2008 by: je
Yellow Belt

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